[SERVER-3606] Dropping an index fails when quota exceeded Created: 15/Aug/11  Updated: 30/Mar/12  Resolved: 22/Aug/11

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

Type: Bug Priority: Major - P3
Reporter: Robert Miyashiro Assignee: Aaron Staple
Resolution: Duplicate Votes: 1
Labels: cloud
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-2012 drop fails when unable to allocate Closed
Operating System: Linux
Participants:

 Description   

When dropping an index, it's possible for the operation to fail due to a "disk space quota exceeded" error. Seems like removal operations that reduce the size of the database shouldn't ever cause this kind of error.

command failed [command
failed [drop]

{ "nIndexesWas" : 1.0 , "msg" : "indexes dropped for collection" , "ns" : "xxx.yyy" , "errmsg" : "exception: db disk space quota exceeded xxx" , "code" : 12501 , "ok" : 0.0}



 Comments   
Comment by Aaron Staple [ 22/Aug/11 ]

Probably similar to SERVER-2012. I will add to that ticket.

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