[DOCS-12352] Docs for SERVER-38512: Implement disconnection behavior for OP_MSG Created: 11/Jan/19  Updated: 13/Nov/23  Resolved: 05/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: Unassigned
Resolution: Duplicate 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
Duplicate
duplicates DOCS-12372 Docs for SERVER-38755: Stop closing c... Closed
Participants:
Days since reply: 5 years, 4 weeks, 5 days ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

I bet there are many places in the docs that say a primary closes connections when it steps down. Such documentation should just be deleted. A more detailed description could also mention that if a client is streaming unacknowledged writes to a server when it steps down, then the server will soon close the connection and the client will receive a network error.

Engineering Ticket Description:

Testing should include:

  • that unacknowledged writes to a secondary result in a disconnection.
  • that unacknowledged writes in progress when a stepdown occurs result in a disconnection.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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


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