scalien/scaliendb — Issue #378: Client may stuck, after primary changes continues
Author: agazso
Created: 2012-02-16 16:38:06+00:00
State: open

This happened to me when adding and removing shard servers from quorums after using activateShardServer with the force flag.

The quorum worked, because I was able to write to the database on the HTTP interface, but the client was timing out. After killing the controller the client handled the controller failover and worked well.