Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
Description
Description
Description:
We need to update the reconfig doc(https://docs.mongodb.com/master/reference/method/rs.reconfig/#availability). Currently its been mentioned as below.
"The rs.reconfig() shell method can trigger the current primary to step down in some situations. When the primary steps down, it forcibly closes all client connections."After PM-639(Avoid closing connections and killing operations on step down), we don't close client connections on step down. And, the new behavior of step down will be addressed by DOCS-12469.
Engineering Ticket Description:
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
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-37574 Force reconfig should kill user operations
-
- Closed
-
- related to
-
DOCS-12710 Docs for SERVER-41035: Rollback should kill all user operations before taking RSTL lock in X.
-
- Closed
-