Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
The kubernetes operator currently always deletes the JM deployment directly during last-state upgrades instead of attempting any type of graceful shutdown.
We could improve the last-state upgrade logic to cancel the job in cases where the JM is healthy and then simply extract the last checkpoint info through the rest api like we already do for terminal job states.
This would allow the last-state upgrade mode to work even for session jobs and this may even eliminate a few corner cases that can result from the current forceful upgrade mechanism.
Attachments
Issue Links
- links to