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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CASSSIDECAR-210: Fix PeriodicTaskExecutor double execution due to race from reschedule #192
CASSSIDECAR-210: Fix PeriodicTaskExecutor double execution due to race from reschedule #192
Changes from 1 commit
4ee948f
a3981b3
b111d39
156ff5d
de3a4dc
4d943a5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the fix. Do not reschedule, but just signal the decision and update the delay when scheduling a new run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have a Result that doesn't mean RESCHEDULED, like COMPLETED? The fact that we call
Promise#tryComplete
with either RESCHEDULED or nothing at all (essentially,null
) seems really odd, even if we never really check for COMPLETED.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COMPLETED
is unnecessary. When the handler atonComplete
is invoked, we know that it is completed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can probably rename the enum. It is not really the result of execution. Looking for suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah - the biggest thing to me was that this enum is used as the type of an AsyncResult and we set the result to
RESCHEDULED
or nothing at all, which was just jarring when I was looking at the code.What do you think of actually using the
ScheduleDecision
enum here, and just getting rid of theResult
all together? Then each branch of theexecuteInternal
method would actually be able to indicate which decision was made - we end up only usingRESCHEDULE
right now but at least there isn't an odd mix ofpromise.tryComplete()
andpromise.tryComplete(Result.RESCHEDULE)
which didn't make a lot of sense to me - if the promise is aPromise<Result>
it should really be completed with something other than null... usingPromise<ScheduleDecision>
makes more sense.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep.
ScheduleDecision
makes better sense.