[DOCS-8468] remove shard { "ok" : 0, "errmsg" : "clone failed" } Created: 01/Aug/16 Updated: 11/Jan/17 Resolved: 04/Aug/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Manjunath Marisetty | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 28 weeks ago |
| Description |
|
In a cluster we have two shards. "note" : "you need to drop or movePrimary these databases", Hence i tried to move the test DB to shard1: ) { "ok" : 0, "errmsg" : "clone failed" }I got the above message,any suggestion please. |
| Comments |
| Comment by Manjunath Marisetty [ 04/Aug/16 ] |
|
I have got this fixed by removing the duplicate collections on the destination shard. You can close this ticket. Thank you. |
| Comment by Ravind Kumar (Inactive) [ 01/Aug/16 ] |
|
Hello, Please note that the DOCUMENTATION project can only provide limited guidance for server-related problems. This guidance should not be taken as official MongoDB support. For official support, please visit the MongoDB Google Group for community support. If you have an active support contract, please contact your MongoDB Account Representative. If possible, could you provide the output from sh.status. Also, it may be of help to ensure that the size of the test database can fit entirely on the shard1 hardware. Please note that sh.status outputs details related to your sharded cluster including full hostnames. Please make ambiguous or retract entirely any information from the output of sh.status that you do not feel comfortable being in this ticket. The documentation project is publicly visible. |