Fix discovery flow for PartitionedHttpClient
#3001
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.
Motivation:
Our load balancers have an ability to cancel and re-subscribe to the
ServiceDiscovery
publisher as an attempt to trigger re-discovery when LB turns into unhealthy state for all addresses. However, forPartitionedHttpClient
it will result inDuplicateSubscribeException
becausegroupToMany
operator does not support re-subscribes.Modifications:
multicast
operator withcancelUpstream=false
flag to allow LB of a single-address client to re-subscribe to the same group publisher;ServiceDiscovery
at single-address client level for partitioned client;NoRetriesStrategy.toString()
for better logging;PublisherGroupToManyTest
;Result:
Single-address clients under partitioned client won't fail with
DuplicateSubscribeException
if LB decides to re-subscribe to the group's stream.