Balancer stuck due to config server crash

From: Darshan Shah <dee.cal@xxxxxxxxx>
To: mongodb-user <mongodb-user@xxxxxxxxxxxxxxxx>
Date: Fri, 22 Apr 2016 08:53:49 -0700 (PDT)
Why ads?
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?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
--- 
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to mongodb-user@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/acc244bc-0dfb-4450-b0e5-db385da3063c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Why ads?