Fix for issue #54: Lifecycle policy scheduler needs to be modified based on activity #119
Conversation
This file contains 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
jfarcand
added a commit
that referenced
this pull request
Dec 9, 2011
Fix for issue #54: Lifecycle policy scheduler needs to be modified based on activity
jfarcand
added a commit
that referenced
this pull request
May 30, 2012
Fix for issue #54: Lifecycle policy scheduler needs to be modified based on activity
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Maintain an atomic boolean that is set to true on every publish. Check in the life cycle handler to see if the atomic boolean has remained false through at least one full interval. If so, proceed with checking the various IDLE_* conditions.
This is a minimal-effort approach, in that we do not alter the handler's scheduling to detect a precise idle interval.