[SERVER-15191] Automatically clean up files in data/moveChunk directory Created: 09/Sep/14  Updated: 09/Jul/16  Resolved: 11/Sep/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.6.4
Fix Version/s: None

Type: New Feature Priority: Trivial - P5
Reporter: John Reno Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-2640 Automatically remove old moveChunk bs... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

I see a large number of files in the data/moveChunk directory. Googling around, I find that this is a dropoff directory for chunks that are being moved to another shard, but there is no provision to clear the space after the chunks are moved.
Questions:
1) At what point can I safely delete the files? There are many files prefixed with 'post.cleanup', are these safe to delete when found?
2) What other file prefixes are used? Are any of those files safe to delete?
3) Are there plans for MongoDB to automatically maintain this directory?
Thanks,
jlr



 Comments   
Comment by Tyler Brock [ 23/Sep/14 ]

Hey John,

Do you have any further questions? If you would like to remove the files in that directory it would be a good idea to stop the balancer before doing so (to prevent new migrations from taking place and wait for existing ones to finish).

You can do this by running sh.stopBalancer(). However, pplease remember to start it again after you have removed the files by running sh.startBalancer().

Comment by Greg Studer [ 11/Sep/14 ]

The "moveParanoia" and "noMoveParanoia" options are available to disable/enable this behavior - the extra chunk datafiles are simply there to provide another level of disaster recovery (particularly when initially unfamiliar with cluster administration). This provides little value though when regular backups are performed.

Confusingly, v2.4 changed the default from "moveParanoia" to "noMoveParanoia", and v2.6 restored the default again. This option may be removed in a future release, but there are no plans to make it more intelligent.

Comment by Ramon Fernandez Marina [ 10/Sep/14 ]

jlreno, the specific case of the files in the data/moveChunk directory is documented here.

I'm going to re-purpose this ticket to see if these files can be safely removed in an automatic fashion.

Generated at Thu Feb 08 03:37:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.