You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I observed this exception with pysyncobj 0.3.13 in the auto tick thread, which killed it. The syncobj was unsable then because the tick thread was not running anymore.
This error seems to be a rare race condition. It happened directly after this syncobj transitioned from candidate to follower status (within the same second). Based on the origin of the exception it looks like this syncobj received a apply_command_response which it didn't like.
3 nodes participated in this raft in total, all pysyncobj 0.3.13.
I don't understand why this AssertionError appeared but I think it should not stop the auto tick thread.
The text was updated successfully, but these errors were encountered:
I observed this exception with pysyncobj 0.3.13 in the auto tick thread, which killed it. The syncobj was unsable then because the tick thread was not running anymore.
This error seems to be a rare race condition. It happened directly after this syncobj transitioned from candidate to follower status (within the same second). Based on the origin of the exception it looks like this syncobj received a
apply_command_response
which it didn't like.3 nodes participated in this raft in total, all pysyncobj 0.3.13.
I don't understand why this
AssertionError
appeared but I think it should not stop the auto tick thread.The text was updated successfully, but these errors were encountered: