-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
ALL
-
Repl 2024-08-05
-
0
We cannot guarantee that heartbeats always come back in the order they are sent. It is possible that a node responded two heartbeats at configTerm 1 and 2, but the heartbeat with configTerm 1 arrived at the receiver at a later point. When we process the heartbeat response and update member data, we are not checking if the configTerm from heartbeat is greater than the current one, which could cause a configTerm regression for certain node and lead to cases like BF-33998.