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
WL#11338: Backport changes to uniquely identify different node incarnations
In GCS/XCOM, a node can receive messages such as ping(s) and paxos
proposals and act upon them immediately after rebooting. However,
a node that has recently rebooted suffers from amnesia and does not
know anything about its prior states unless it has written them into
a stable storage. Unfortunately, GCS/XCOM does not use any stable
storage in order to improve performance but pings and paxos are still
indiscriminately processed after reboot. This scenario can lead to a
variety of strange problems, and in the extreme case, it can generate
data inconsistency.
We have identified the problem and started augmenting GCS/XCOM with
the notion of incarnation. Basically, every node has a unique
identifier assigned to it every time it joins the cluster and this
information can be used to distinguish among different node
incarnations.
This fix contains the following set of patches backported from 8.0:
. BUG#25311008
. BUG#22204121
0 commit comments