[SERVER-7728] Add more details on why a shard is 'unavailable' for balancing Created: 20/Nov/12  Updated: 11/Jul/16  Resolved: 30/Apr/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.3.1
Fix Version/s: 2.4.6, 2.5.0

Type: Bug Priority: Minor - P4
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

This is the current code in DistributionStatus::getBestReceieverShard @ balancer_policy.cpp:

if ( i->second.isSizeMaxed() || i->second.isDraining() || i->second.hasOpsQueued() ) {
  LOG(1) << i->first << " is unavailable" << endl;
  continue;
}

It would probably be nice if we split these up and display a different log message for each case.



 Comments   
Comment by auto [ 02/Aug/13 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-7728 Add more details on why a shard is 'unavailable' for balancing
Branch: v2.4
https://github.com/mongodb/mongo/commit/fa40f42573419fe61abc63195f18d051bc886dbf

Comment by Anton V. Volokhov [ 10/Jun/13 ]

Could you backport this fix to 2.4.x branch? It is minor yet useful commit.

Comment by auto [ 30/Apr/13 ]

Author:

{u'date': u'2013-04-04T20:31:06Z', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-7728 Add more details on why a shard is 'unavailable' for balancing
Branch: master
https://github.com/mongodb/mongo/commit/deee10f83dcb62bd6dd2808850fe59618449756e

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