145dced3e8
This is what it was likely causing PeerRemove tests to fail randomly but very often. We cancelled the Cluster context before shutting down the Consensus component. This killed networking and aborted the peer remove operations when the leader is removing itself. As a result, it would error with "leadership lost", which would trigger a retry which would set the final error to "context cancelled" because the shutdown of the consensus component proceeds during the retry, cancelling the consensus context. This is not only affecting tests, it might affected operations when running cluster. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> |
||
---|---|---|
.. | ||
raft |