[SERVER-56116] Balancing failed when moving big collection Created: 15/Apr/21 Updated: 11/May/21 Resolved: 11/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Wernfried Domscheit | Assignee: | Eric Sedor |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I like to archive my data as described in Tiered Hardware for Varying SLA or SLO My sharded cluster looks like this:
In order to trigger migration I use
I don't get any error and migration starts. However, in my logs (at config server) I get thousands or even millions of these warnings:
The file system reached 100% and MongoDB stopped working. How can this be? `MinKey` / `MayKey` should cover all values.
|
| Comments |
| Comment by Eric Sedor [ 11/May/21 ] |
|
I understand wernfried.domscheit@sunrise.net. I'm going to close this ticket for now, but we are happy to reopen the ticket or address a new one if you experience the problem again. Thank you, |
| Comment by Wernfried Domscheit [ 05/May/21 ] |
|
Today I tried the procedure again and it was working fine as expected. So, I am not able to reproduce this error. I don't know whether I should be happy about this or not, because I don't like to run into this issue suddenly on production. No idea if we should keep this ticket open. Best Regards
|
| Comment by Wernfried Domscheit [ 29/Apr/21 ] |
|
Currently I run some other topics, I think next week I can provide the required information. |
| Comment by Eric Sedor [ 27/Apr/21 ] |
|
Hi wernfried.domscheit@sunrise.net, The error message you've found suggests that there isn't a problem with the range tagging, but rather a problem identifying shard04 as a destination. It's not immediately clear this is the result of a bug, but we can take an initial look. Can you please provide a mongodump of the config database as well as the logs from the config server? |
| Comment by Wernfried Domscheit [ 21/Apr/21 ] |
|
Just a note, when I tested this procedure with a smaller collection (i.e. 1 Million documents) it is all working fine. But it fails at bigger collection with 50M documents. Best Regards |