For clusters with significant load on secondary nodes of replica set shards, the default secondary throttle mode (w:1) may not ensure that chunk migration doesn't interfere with all secondaries. Support other write concern "w" modes (1, 2, "majority") for this parameter to allow configurable throttling. Also the default is changed to { _secondaryThrottle: true } for chunk migration.
- is duplicated by
-
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
- is related to
-
SERVER-16842 moveChunk with replication is slow with 2.8
- Closed
-
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
-
SERVER-16548 Allow enforcement of additional custom write concern at pre-commit
- Closed
-
SERVER-14567 Implement checkIfWriteConcernCanBeSatisfied
- Closed
-
SERVER-16357 Chunk migration pre-commit write concern should be configurable
- Closed
- related to
-
SERVER-15591 enforce secondaryThrottle during moveChunk commit
- Closed