[DOCS-11938] Description and example for waitForSecondaryBeforeNoopWriteMS do not match Created: 03/Aug/18 Updated: 30/Oct/23 Resolved: 08/Oct/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Oleg Pudeyev (Inactive) | Assignee: | Isabella Siu (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 18 weeks, 2 days ago |
| Description |
|
---------------------------- Original Descriptionhttps://docs.mongodb.com/manual/reference/parameters/#param.waitForSecondaryBeforeNoopWriteMS The description for waitForSecondaryBeforeNoopWriteMS says: "The length of time (in milliseconds) that a secondary must wait if the afterClusterTime is greater than the last applied time from the oplog." However the example given is: > The following example sets the waitForSecondaryBeforeNoopWriteMS to 20 seconds: > mongod --setParameter waitForSecondaryBeforeNoopWriteMS=20 Wouldn't that set the wait to 20 milliseconds, not 20 seconds? Descriptionhttps://docs.mongodb.com/manual/reference/parameters/#param.waitForSecondaryBeforeNoopWriteMS The description for waitForSecondaryBeforeNoopWriteMS says:
However the example given is:
The example should be updated to read
Scope of changes (files that need work and how much)Impact to other docs outside of this productMVP (work and date?)Resources (e.g. Scope Docs, Invision) |
| Comments |
| Comment by Githook User [ 08/Oct/18 ] |
|
Author: {'name': 'Isabella Siu', 'email': 'isabellasiu@Isabellas-MacBook.local'}Message: |
| Comment by Githook User [ 08/Oct/18 ] |
|
Author: {'name': 'Isabella Siu', 'email': 'isabellasiu@Isabellas-MacBook.local'}Message: |