[DOCS-11038] Docs for SERVER-32006: Add a parameter to wait before secondaries perform noop write Created: 20/Nov/17  Updated: 29/Oct/23  Resolved: 23/Nov/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.6.0-rc5, 3.7.1

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-32006 Add a parameter to wait before second... Closed
Participants:
Days since reply: 6 years, 12 weeks ago
Epic Link: DOCS: 3.6 Server

 Description   

Documentation Request Summary:

--setParameter waitForSecondaryBeforeNoopWriteMS defaults to 10 milliseconds. This is the time a secondary node waits before making noop write in the case afterClusterTime specified in a readConcern does not mathc the last applied time from the oplog.

Engineering Ticket Description:

Current implementation if afterClusterTime waits makes noop write immediately after detecting that the requested time is > then available time in an oplog. Instead the wait should be adjustable to avoid unnecessary writes.
Adding a WaitForSecondaryBeforNoopWriteMS parameter and waiting its value will solve it.



 Comments   
Comment by Githook User [ 23/Nov/17 ]

Author:

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

Message: DOCS-11038: waitForSecondaryBeforeNoopWriteMS parameter
Branch: master
https://github.com/mongodb/docs/commit/b5fb25eb2227634870b701420eeb0cd366c7c0dd

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