GEODE-8951: Unnecessary messaging in WAN locator discovery #6496
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.
The ticket states that when a locator joins the cluster, it is notified about itself joining the system.
That problem was already solved by GEODE-6977, in
locatorJoined(...)
method ofLocatorMembershipListenerImpl
class, before starting the thread that will send the notifications about the new locator:Anyway, in order to verify that no more than the expected number of notification messages are sent, a check can be added to three unit tests of
LocatorMembershipListenerImpl
class. These test cases verify that the proper messages are sent, but they would not fail if unexpected messages were sent.