This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Fix bug in publisher to support cool off period on a per node basis #351
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.
Issue #:
#352
Description of changes:
The current implementation of cool off action map only take action.name() as the hashkey and map it to the execution time. This is incorrect because if let's say we have two actions of the same type but has different target (impacted) nodes. One action will be published while the other will be blocked. This is not the expected behavior as both actions should be published if their impacted nodes are not overlapped. We should use action.name() + nodekey as the hashkey instead.
In this PR, I moved the cool off action map into a separate class namely CoolOffDetector and extend the hashmap to support hashkey as action.name() + nodekey.
Tests:
n/a
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.