[SERVER-11733] Add a writeConcern mode that works on all cluster and node types that can be used to ensure the data is written as safely as possible Created: 15/Nov/13 Updated: 10/Dec/14 Resolved: 04/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Security, Sharding |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Right now the shell helpers for user management use a default write concern of "majority". This becomes a problem, however, when managing users on master/slave deployments or on config servers, as w:'majority' does not work or have any reasonable meaning in those setups. We need a write concern mode that means "majority" on replica sets and something sane on master/slave, standalone, mongos, and config servers so that we can use that for user management. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 04/Dec/13 ] |
|
Rather than doing this, we're going to make w: "majority" work for all node types, according to |