Closed RyanTT closed 2 years ago
@RyanTT , what kind of transport are you using? HTTP/UDP/TCP?
I am using HTTP transport.
@RyanTT , regression has been fixed.
I believe the issue is still present. I've updated my projects to beta.2 and the behavior has remained the same:
After step 3, node 1 is unable to write to the log System.InvalidOperationException: The local cluster member is not a leader
.
@RyanTT , do you have a repro code for that?
Sorry for the late response. I'll attempt to write a test to reproduce this issue in the following days.
Hi @RyanTT , did you have a chance to reproduce the issue?
Closing this issue due to lack of activity.
Hello,
I am currently trying to run the
4.2.0-beta.1
version and I have come across a specific issue regarding the log entry writing with Raft and the events associated with itAfter step 3 and inspecting my logs, it seems like the leader steps down to follower but does not fire the
IRaftCluster.LeaderChanged
event.IRaftCluster.Members
will still report the local (Remote == false) node 1 as leader on node 1, but attempting to write to the log now will result inIClusterMember.MemberStatusChanged
will correctly fire and set node 2 to Unavailable during step 3. This behavior was not present before the upgrade to4.2.0-beta.1
.After step 4 is done, (on node 1)
IClusterMember.MemberStatusChanged
will correctly fire and mark node 2 as available again. However, node 1 is still unable to write to the log as it seemingly isn't leader anymore. Only some time after this step, node 1 will correctly fireIRaftCluster.LeaderChanged
to NO LEADER, and then fire it again but WITH A LEADER.