Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
If the command gets stuck in making a db call during loadState() after acquiring the lock, the lock will never be released and the job will be stuck forever.
Need to introduce a timeout for the database call.
There might be also be an issue with the implementation of MemoryLocks.
Attachments
Issue Links
- relates to
-
OOZIE-1507 Command queue filling up with duplicate commands from RecoveryService
- Closed