Restore scheduling - #1058
Open
ihardy wants to merge 5 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Grails 5 upgrade removed @EnableScheduling from the application. As a result, grails-okapi’s scheduled heartbeat and federation cleanup tasks never ran. After pod restarts, instance records and locks became stale, and tenant requests could wait indefinitely for locks that would never be released.
The fix restores @EnableScheduling, allowing each pod to update its heartbeat and the federation leader to identify and clean up stopped instances and their locks. Existing orphaned locks may still require a one-time manual cleanup.