Re: Balancer stuck due to config server crash

From: Kevin Adistambha <kevinadi@xxxxxxxxxxx>
To: mongodb-user <mongodb-user@xxxxxxxxxxxxxxxx>
Date: Thu, 28 Apr 2016 22:41:05 -0700 (PDT)
Why ads?


Hi Darshan

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.

Have this issue been resolved? Or is this is still happening?

If you think this is still an issue, could you tell us:

   - the output of sh.status() 
   - what you mean by “showing that particular collection as also being 
   migrated.” 

Since config servers are absolutely vital to the operation of a sharded 
cluster, I would recommend you to upgrade your config servers to a replica 
set 
<https://docs.mongodb.org/manual/tutorial/upgrade-config-servers-to-replica-set/
to improve performance and consistency on the config servers.

Best regards,
Kevin


-- 
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/87d34c34-44cb-4e45-b898-39c48c594f54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Why ads?