[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: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
This is the current code in DistributionStatus::getBestReceieverShard @ balancer_policy.cpp:
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: |
| 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: |