Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.3.0
Description
The JobLeaderIdService has no mechanism to time out inactive jobs. At the moment it relies on the RunningJobsRegistry which only gives a heuristic answer.
We should remove the RunningJobsRegistry and register instead a timeout for each job which does not have a job leader associated.
Attachments
Issue Links
- links to