-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Have a new write concern w:default, which is based on the configuration. Drives would specify this and the server would determine what this means. Having a default write concern that is concrete forces w:1 to account for standalones. This would allow for a more intuitive write concern depending on the MongoDB configuration (not the current state of that configuration).
w:default would translate to:
| Standalone | w:1 |
|---|---|
| Replica set w/ arbiter | w:1 |
| Replica set w/o arbiter | w:majority |
The argument could be made for Replica w/ arbiter to be half of the number of data bearing nodes as this is static with config too.
- related to
-
SERVER-14708 A mixed single node & replicaset set sharded cluster can wait for replication on the single node when moving chunks, if secondaryThrottle is enabled
-
- Closed
-