Force WorkerBolt
to be more strict with stored data
#2546
Merged
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.
Lock all operations with
pendingTasks
map into theWorkerBolt
i.e.do not allow access there to the inheritors. If inheritors have access
to this map there is no way to implement LCM for objects stored there.
The original problem was lack of cleanup on timeout action.
Also make correct routing/dispatching of
onTimeout
event, till nowthis dispach have happended inside
dispatch
method oforg.openkilda.wfm.share.hubandspoke.CoordinatedBolt
(happens beforehandleInput
) as result all checks and cleanup steps implemented onhandleInput
level are skipped.This change is