-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.0, v3.6
-
Repl 2018-10-22, Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08, Repl 2019-04-22, Repl 2019-05-06, Repl 2019-05-20, Repl 2019-06-03
-
12
Force reconfig from the command and from a heartbeat can lead to a stepdown and thus needs to kill user operations.
Here: https://github.com/mongodb/mongo/blob/a222ef5e647ac527f7d4f8636bcacd6cc0ae6b8e/src/mongo/db/repl/replication_coordinator_impl.cpp#L2329-L2335
And here:
https://github.com/mongodb/mongo/blob/a222ef5e647ac527f7d4f8636bcacd6cc0ae6b8e/src/mongo/db/repl/replication_coordinator_impl_heartbeat.cpp#L559-L568
- is depended on by
-
SERVER-41037 Stepup should kill all user operations(that encounters prepare conflict) before taking RSTL lock in X.
- Closed
-
SERVER-40487 Stop running the RstlKillOpthread when a node is no longer primary
- Backlog
- is related to
-
SERVER-27534 All writing operations must fail if the term changes
- Closed
-
SERVER-41234 Concurrent step downs due to step down via heartbeat and force reconfig should ensure that the term maintained by topology coordinator is set to TopologyCoordinator::_pendingTermUpdateDuringStepDown.
- Closed
- related to
-
SERVER-41035 Rollback should kill all user operations before taking RSTL lock in X.
- Closed
-
SERVER-37381 Allow prepared transactions to survive state transitions
- Closed