[SERVER-19963] More detailed log information when querying shard info fails Created: 14/Aug/15  Updated: 25/Jan/17  Resolved: 14/Aug/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.1.6
Fix Version/s: 3.1.7

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 8 08/28/15
Participants:

 Description   

Code in question:

https://github.com/mongodb/mongo/blob/r3.1.6/src/mongo/s/client/shard_registry.cpp#L95

Example logs:

2015-08-13T17:48:08.668+0000 W SHARDING [Balancer] could not initialize balancer, please check that all shards and config servers are up: couldn't get updated shard list from config server
2015-08-13T17:48:08.668+0000 I SHARDING [Balancer] will retry to initialize balancer in one minute



 Comments   
Comment by Githook User [ 14/Aug/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-19963 Provide more detailed debug information when shard registry cannot fetch all shards.
Branch: master
https://github.com/mongodb/mongo/commit/486cbe281e2f19f295838eeef59340a90201ce40

Comment by Randolph Tan [ 14/Aug/15 ]

This has been observed in some of the test, and causes some to timeout waiting for balancer to get turned off.

Generated at Thu Feb 08 03:52:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.