FISH-1293 Disassociate ClusteredStore from tenants #5188
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.
Description
Bug.
Tenant control associates all Hazelcast objects to their calling applications by default.
However, internal maps that belong to
ClusteredStore
should not do this.This fix prevents it from associating thus preventing blocking by tenant control
when application is undeployed
pushing empty context in ClusteredStore to prevent association of Hazelcast maps to tenant applications
that may be later undeployed and would leave maps orphan, which in turn will lead
to Hazelcast blocking calls to those maps
minor cleanup
Testing
Testing Performed
Ran Payara Samples twice, which is how I discovered this bug in the first place
Review Notes
** Please use "ignore whitespace changes" to review,
otherwise it looks like changes don't make sense