[SERVER-426] REQ: temp Repair directory to be config file or user defined. Created: 17/Nov/09  Updated: 12/Jul/16  Resolved: 25/Jan/10

Status: Closed
Project: Core Server
Component/s: Admin, Usability
Affects Version/s: 1.1.3
Fix Version/s: 1.3.2

Type: Improvement Priority: Minor - P4
Reporter: Alexey Zilber Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Participants:

 Description   

Current;y, mongodb repairs databases by creating a temporary directory within it's database path directory. This is highly bad for many reasons:

1) On AWS with EBS volumes this will double or triple repair time, and cost more money if a lot of data is to be repaired. Also, by 'activating' more ebs blocks then will actually be used, snapshots will double in size and costs will double here as well.
2) For performance, the temp directory might be on a separate volume, ram disk, etc.
3) The data directory might be on iscsi (ala SoftLayer) and performance and space consideration would be an issue.
4) There might simply not be double the database space on the volume.

Relocating the temp directory and making the variable user configurable is the sane thing to do here.

-Alex



 Comments   
Comment by Aaron Staple [ 25/Jan/10 ]

Ok, there's now a --repairpath option. The repairpath must exist before you start the db. Let us know if you have any trouble.

Comment by auto [ 25/Jan/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-426 make repair path configurable
http://github.com/mongodb/mongo/commit/3b4a0b04dde91b7109c6ad08e366ab64e3c96808

Comment by Alexey Zilber [ 17/Nov/09 ]

#2 above is just a comment, not a negative reason.

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