Description
In a sharded cluster with replica sets, if any standard node goes down, when run command "moveChunk" or create sharded collection with "hashed" key, the operation does not end.
The weak replica set's primary node shows below on log file.
Sat Oct 19 01:34:28.611 [rsHealthPoll] couldn't connect to localhost:26202: couldn't connect to server localhost:26202
Sat Oct 19 01:34:29.292 [migrateThread] Waiting for replication to catch up before entering critical section
Sat Oct 19 01:34:29.293 [migrateThread] warning: migrate commit waiting for 2 slaves for 'foo.bar' { name: 0 } -> { name: MaxKey } waiting for: 526162d9:2
I tried this for 2.4.2 but It works well. This happens only 2.4.6.
Attachments
Issue Links
- is related to
-
SERVER-16357 Chunk migration pre-commit write concern should be configurable
-
- Closed
-