[SERVER-10410] better reporting of mongod collection metadata state Created: 02/Aug/13 Updated: 11/Jul/16 Resolved: 02/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
... via an optional parameter to getShardVersion(). This should help us verify cases where the mongod metadata is confused. |
| Comments |
| Comment by auto [ 02/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: ...from getShardVersion |