The existing resolution for a split-brain scenario is one that simulates a 'leave-the-cluster' event, followed by a 'join-the-cluster' event.
A problem in the implementation is that 'joining' happens to soon after the 'leave' is issued. Various (asynchronous) processes are still cleaning up data, while the join-routines are being executed. It has been observed that certain data that's added by virtue of the 'join' is being removed again as the 'leave' is still being executed.
The existing resolution for a split-brain scenario is one that simulates a 'leave-the-cluster' event, followed by a 'join-the-cluster' event.
A problem in the implementation is that 'joining' happens to soon after the 'leave' is issued. Various (asynchronous) processes are still cleaning up data, while the join-routines are being executed. It has been observed that certain data that's added by virtue of the 'join' is being removed again as the 'leave' is still being executed.