[SERVER-19285] setShardVersion failed host: 127.0.0.1:30004 { errmsg: "exception: remote client 127.0.0.1:40881 tried to initialize this host (127.0.0.1:30004) as shard shard0040, but shard name was previously initial...", code: 13298, ok: 0.0 } Created: 06/Jul/15 Updated: 07/Jul/15 Resolved: 07/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Dnv.IytH | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
First, I remove some shards(shard0020 - 99) which don't contain any data with command `sh.removeShardTag("shard0020-99", "tag1")` and `db.runCommand( {removeShard: "shard0020-99"})`. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 07/Jul/15 ] |
|
The procedure for removing a shard is described in this tutorial. Using sh.removeShardTag() is not part of this procedure. I hope the tutorial will clarify the issue you're seeing. I'm going to close this issue for now, but if you have additional issues with your sharding configuration and management, feel free to contact one of our support channels. Regards, |