ttl: fix the issue that the TTL jobs are skipped or handled multiple times in one iteration (#59348) #59353
+58
−4
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.
This is an automated cherry-pick of #59348
What problem does this PR solve?
Issue Number: close #59347
Problem Summary:
Some of the TTL jobs are skipped for handled multiple times in one iteration. It caused the following effect:
CheckNotOwnedJob
,checkFinishedJob
,rescheduleJobs
to handle all existing jobs.I think it's a minor issue as both of them don't block the TTL.
What changed and how does it work?
Iterate the jobs in the reverse order.
Check List
Tests
Release note