[DOCS-12372] Docs for SERVER-38755: Stop closing connections on stepdown gated by server parameter "closeConnectionsOnStepdown" flag. Created: 16/Jan/19  Updated: 13/Nov/23  Resolved: 06/Aug/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.7, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-38512 Implement disconnection behavior for ... Closed
documents SERVER-38755 Stop closing connections on stepdown ... Closed
Duplicate
is duplicated by DOCS-12352 Docs for SERVER-38512: Implement disc... Closed
Related
Participants:
Days since reply: 4 years, 27 weeks, 1 day ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

When the closeConnectionsOnStepdown parameter is false, this change makes replSetStepDown not disconnect any clients. So the replSetStepDown command documention "Client Connections" section needs to be corrected. Same for the rs.stepDown() shell method.

This change will not be the default until SERVER-38517 is complete, which is expected by 4.2 GA.

Engineering Ticket Description:

Tests should include

  • Test that writes in progress are terminated with InterruptedDueToStepdown, but the connection is not closed.
  • Test that a linearizable read in progress is terminated with InterruptedDueToStepdown.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 06/Aug/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12372: 4.2 replSetStepDown and client connections
Branch: master
https://github.com/mongodb/docs/commit/fdcd0dd4d218929f46aabbf855b0d46e5414949c

Generated at Thu Feb 08 08:05:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.