I am running a MongoDb 3.2.5 tag-aware sharded cluster with WiredTiger
having 3 config servers (which are not in a replicaset) and each node being
a 2 node replicaset.
In the sharded cluster, the config servers were restarted while the
balancer was balancing a tag-aware collection.
After the config servers were restarted, I see that the balancer is stuck
on balancing that same collection for over few hours.
I manually removed the balancer lock and then it proceeded with balancing
other collections and still keeps showing that particular collection as
also being migrated.
Is this behavior normal?
How do we cleanly recover in such a scenario?
You received this message because you are subscribed to the Google Groups "mongodb-user"