[SERVER-12758] CleanupOldData Created: 18/Feb/14 Updated: 10/Dec/14 Resolved: 30/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, Sharding, Storage |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Steffen | Assignee: | Thomas Rueckstiess |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We use Mongodb 2.4.6 But on one of the 2 old shards we see a lot cleanup messages in the log, thus we have high IO on this server
It seems the the cleaner goes through the whole hashed shard key range. We also disabled "_secondaryThrottle" afterwards on the balancer setting, but it seems that this is not recognized on the replicaset
2. Is there a way to disable it afterwards? |
| Comments |
| Comment by Thomas Rueckstiess [ 30/May/14 ] |
|
Hi Steffen, The log messages you posted look like normal behavior of chunk migrations. The cleanup cannot be skipped with the methods you mention, the data needs to be removed from the donor shard of the migration. As for your question about _secondaryThrottle: The documentation mentions:
The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. Regards, |