[SERVER-27105] balancing error: Failed with error 'ns not found, should be impossible' Created: 18/Nov/16 Updated: 04/Dec/16 Resolved: 04/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Tal Grynbaum | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | not sure, |
||||
| Participants: | |||||
| Description |
|
I had a mongodb with 2 shards, with a huge collection (14B rows). active mongoses: |
| Comments |
| Comment by Kelsey Schubert [ 04/Dec/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi talg70, Thank you for confirming that this issue has been resolved. Kind regards, | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Tal Grynbaum [ 04/Dec/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Thomas I was able to drop the collections with a drop command from mongos, and no, I haven't experienced the issue again. Thanks | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 04/Dec/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi talg70, Have you experienced this issue since following the steps outlined in Thank you, | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 22/Nov/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi talg70, Since these collections are not needed, I would recommend dropping them by following the workaround described in Kind regards, | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Tal Grynbaum [ 20/Nov/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
another strange behavior: running db.testshard.find()
| ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Tal Grynbaum [ 20/Nov/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Before attempting to do a manual moveChunk,
so I suspected that the bad collection is newDailyUsers, and indeed, running the following command:
and also on the testshard collection
As I don't need these collections, should I drop them on the mongos or on each of the primaries? | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 18/Nov/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi talg70, Thanks for opening this ticket. I've reviewed the previous discussion on google groups and agree that this is likely related to collection drops. Would you please attempt to manually move a chunk for one of the affected collections using the moveChunk command? Thank you, |