[SERVER-14262] Running a compact command on a 2.4 collection in 2.6.1 caused the command to go into a loop and allocate more db files Created: 16/Jun/14  Updated: 10/Dec/14  Resolved: 19/Aug/14

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.6.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James O'Leary Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL 6.3, mongodb 2.6.1


Operating System: ALL
Participants:

 Description   

I was running a compact command on a 2.4 collection imported into a 2.6.1 server.

The collection was ~ 56GiB and contained 31 datafiles originally.

When I ran compact, the command seems to go into a loop allocating new files datafiles:

2014-06-15T15:06:44.997-0400 [FileAllocator] allocating new datafile /data/mongo/dbpath/XXXXXXX.256, filling with zeroes...

I stopped the compact command at this point. This was also the second run of compact after resetting the db files (I stopped it at about 100 datafiles on that run).

Compacting the same collection on a 2.4.10 instance did not behave this way.



 Comments   
Comment by Ramon Fernandez Marina [ 19/Aug/14 ]

jim.oleary@10gen.com, I'm not able to reproduce this issue on a sample 34GB database, so I'm going to mark this ticket as resolved. If this is still an
issue for you feel free to reopen the ticket and provide further information.

Regards,
Ramón.

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