[DOCS-5314] WriteConcern: clarify that 'w' and 'j' are orthogonal Created: 30/Apr/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

RE: http://docs.mongodb.org/manual/core/write-concern/

The above page may induce confusion due to the mixed use of w and j options to produce overall effects. I think the different levels would be OK but we should clarify that w and j are having different effects and do not directly collude.

This page does a better job of making this distinction clearer: http://docs.mongodb.org/manual/reference/write-concern/
Perhaps direct links to this page from the first one, regarding the individual options may be enough.

w is effectively a "network level" setting, specifying how commands can be acknowledged by members within a set (1, default, meaning only the one you are connected to).

j is effectively a "local" setting, specifying how commands must be durably written to the instance one is connected to but has no impact on the write-concern except in the case where w:0 is zero (j overrides w).

In combination, this means that w set to "majority" and j set to true is meaningful. Though the linked page gives the impression that perhaps it isn't.

w and j are orthogonal.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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