Timeline for MongoDB document delete and fragmentation
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2015 at 9:41 | vote | accept | Andrea Girardi | ||
| Aug 10, 2015 at 20:36 | comment | added | Antonios | Capped collections are limited to size and not to date so you might lose data if you don't do the maths well. What is your average document size? | |
| S Aug 10, 2015 at 20:18 | history | suggested | Markus W Mahlberg |
Removed tag as the version used is 2.6.9
|
|
| Aug 10, 2015 at 19:56 | review | Suggested edits | |||
| S Aug 10, 2015 at 20:18 | |||||
| Aug 10, 2015 at 19:30 | answer | added | Markus W Mahlberg | timeline score: 4 | |
| Aug 10, 2015 at 14:40 | comment | added | Andrea Girardi | Updated question with DB version (2.6.9) | |
| Aug 10, 2015 at 14:40 | history | edited | Andrea Girardi | CC BY-SA 3.0 |
added 20 characters in body
|
| Aug 10, 2015 at 0:27 | comment | added | Stennie | What specific version of MongoDB are you using (and if >3.0, what storage engine)? | |
| Aug 6, 2015 at 9:05 | comment | added | aldwinaldwin | Basicaly : 1. for 100% fixed collection size, use capped collection 2. use latest version of Mongodb where space is reused as good as possible 3. do some maintenance every few weeks (compact/repair/...) 4. if there is constant timeout on the function that is responsible on allocating free space 5. some more rare issues mentioned in that article | |
| Aug 6, 2015 at 9:00 | comment | added | aldwinaldwin | Maybe the following conversation can help you some more: dba.stackexchange.com/questions/106736/… | |
| Aug 6, 2015 at 8:35 | answer | added | Antonios | timeline score: 3 | |
| Aug 5, 2015 at 12:33 | history | edited | Andrea Girardi | CC BY-SA 3.0 |
added 64 characters in body
|
| Aug 5, 2015 at 8:43 | history | asked | Andrea Girardi | CC BY-SA 3.0 |