[SERVER-2834] printShardingStatus is out of date after wiping out the DB Created: 25/Mar/11 Updated: 12/Jul/16 Resolved: 02/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Problem: > db.printShardingStatus() shards: { "_id" : "shard0000", "host" : "10.194.187.111:27000" } { "_id" : "shard0001", "host" : "10.116.78.81:27000" }databases: { "_id" : "admin", "partitioned" : false, "primary" : "config" } { "_id" : "scaleout", "partitioned" : true, "primary" : "shard0001" } scaleout.blogs chunks: Other operations fail because of this stale data e.g. moveChunk { "ok" : 0, "errmsg" : "that chunk is already on that shard" }The config DB still see's the database and sharded collection > db.databases.find() { "_id" : "admin", "partitioned" : false, "primary" : "config" } { "_id" : "scaleout", "partitioned" : true, "primary" : "shard0001" }> db.chunks.find() , "ns" : "scaleout.blogs", "min" : { "ts" : { $minKey : 1 }}, "max" : { "ts" : -2147480140 }, "shard" : "shard0000" } , "ns" : "scaleout.blogs", "min" : { "ts" : -2061389163 }, "max" : { "ts" : -2059556975 }, "shard" : "shard0000" } , "ns" : "scaleout.blogs", "min" : { "ts" : -2021389163 }, "max" : { "ts" : -2020322009 }, "shard" : "shard0001" } Reproduce:
Workaround:
Business case:
|
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 02/Sep/11 ] |
|
was fixed for 2.0 |