[DOCS-12539] "raisings" typo on "Replica Set Protocol Version" page Created: 12/Mar/19  Updated: 30/Oct/23  Resolved: 12/Mar/19

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Trivial - P5
Reporter: Chris Harris Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 4 years, 48 weeks, 1 day ago

 Description   

Description

In the "Back to Back Elections" section:

Starting in MongoDB 3.4, you can also reduce the likelihood of rollback of w:1 writes with pv1 by raisings the catchUpTimeoutMillis setting.

 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 12/Mar/19 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-12539: Fix typo on Replica Set Protocol Version page
Branch: v3.4
https://github.com/mongodb/docs/commit/74e2d138fd318080dcfdbbf077b25744fd9e5905

Comment by Githook User [ 12/Mar/19 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-12539: Remove Outdated Guidance from Replica Set Protocol Version Page
Branch: v3.6
https://github.com/mongodb/docs/commit/8d53813b98cf322fefff1c9539b5a84f17d02ccb

Comment by Githook User [ 12/Mar/19 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-12539: Remove Outdated Guidance from Replica Set Protocol Version Page
Branch: v4.0
https://github.com/mongodb/docs/commit/d6b7e22cfd7589e258caaac518c2f821cb2612f3

Comment by Githook User [ 12/Mar/19 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-12539: Remove Outdated Guidance from Replica Set Protocol Version Page
Branch: master
https://github.com/mongodb/docs/commit/796c0bef287f0cc74d7c931b82a949dc0a3ca7de

Comment by Tess Avitabile (Inactive) [ 12/Mar/19 ]

Yes, I agree, and your plan for changing this text sounds good.

Comment by Ravind Kumar (Inactive) [ 12/Mar/19 ]

tess.avitabile am I right in thinking that this paragraph is actually not all that useful starting in 3.6, given that the default for catchUpTimeoutMillis defaults to -1 (e.g. infinite catchup time)?  So out of the gate the user should have the best possible settings for avoiding rollbacks.  AM inclined to fix this typo for 3.4 only and remove that guidance for 3.6 onwards.

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