Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Incorrect view of initial contact points when subscribing to cluster client #22991
Comments
huntc
referenced
this issue
May 22, 2017
Merged
Corrected the setup of contact paths for subscribers #22992
johanandren
added 3 - in progress t:cluster-tools
labels
May 22, 2017
This was referenced May 29, 2017
johanandren
closed this
in #22992
Jun 4, 2017
johanandren
added a commit
that referenced
this issue
Jun 4, 2017
|
|
huntc + johanandren |
f4bf497
|
johanandren
reopened this
Jun 4, 2017
johanandren
added this to the
2.4.19
milestone
Jun 4, 2017
fadyZohdy
added a commit
to fadyZohdy/akka
that referenced
this issue
Jun 4, 2017
|
|
huntc + fadyZohdy |
208b6c3
|
patriknw
referenced
this issue
Jun 7, 2017
Merged
Corrected the setup of contact paths for subscribers (for validation) #23113
patriknw
removed the
3 - in progress
label
Jun 7, 2017
patriknw
closed this
Jun 7, 2017
patriknw
added a commit
that referenced
this issue
Jun 12, 2017
|
|
huntc + patriknw |
178c811
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
huntc commentedMay 22, 2017
Akka cluster client does not provide the correct initial view of contact points w.r.t. to another actor subscribing to its events. This is accidental and due to a previous PR by me where the ability to subscribe to notifications was provided. There is a variable named
contactPathsPublishedwhich is empty on startup. I see now thatcontactPathsPublished's initial value should be that ofcontactPaths, otherwise a subscriber will receive any initial contact points from config, and thenContactPointAddedmessages for events regardless of whether they in the initial contact points.By initialising
contactPathsPublishedwithcontactPathsthen subsequent contact point notifications will yieldContactPointRemovedfor those contact points that are unknown to the cluster client. I see this as being the correct behaviour, and have tested it by copyingClusterClientinto ConductR.