-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Member.UpNumber fix #1799
Member.UpNumber fix #1799
Conversation
{ | ||
return new Member(uniqueAddress, 0, status, roles); | ||
return new Member(uniqueAddress, upNumber, status, roles); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wow, nice catch. I could see this being responsible for some fun issues with Cluster rejoin scenarios too.
Looks like the timestamp on this commit is 29 days old, so it didn't show up on TeamCity - would you mind changing the timestamp on your commit? http://stackoverflow.com/a/31540373/377476 This will allow our CI system to scoop it up. Great job @zbynek001 👍 |
This is ready for merge once CI passes - it fixes an obvious bug in Akka.Cluster but the test suite might reveal others, and possibly faulty assumptions with the test suite. |
ActorPath operator / fix for empty element ClusterSharding MemberAgeComparer reverse order
@@ -254,7 +254,8 @@ public bool Equals(ActorPath other) | |||
var a = path; | |||
foreach (string element in name) | |||
{ | |||
a = a / element; | |||
if(!string.IsNullOrEmpty(element)) | |||
a = a / element; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've also added fix for ActorPath operator / used in singleton proxy. This way it's also handled in akka
Fixes issue #1784.
Member.UpNumber is not being propagated across cluster
MemberAgeComparer is sorting in a reverse order then it should