Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
3.4.3
-
None
-
ALL
-
Description
If a member is down in a replicaset of a sharded cluster, the chunk migration from the replicaset with the node down to another replicaset, fails with:
moveChunk command failed on source shard. :: caused by :: WriteConcernFailed: waiting for replication timed out
|
Even if the _secondaryThrottle is false and there is no write concern or there is wait concern 1 (both in the config.settings db and in the moveChunk command when executed manually)
This is happening for the regular balancer, and after stopping it and running moveChunk manually i get the same output.
Attachments
Issue Links
- is related to
-
SERVER-22876 Ensure 'majority' writes are possible before entering the migration critical section
-
- Closed
-