[SERVER-12503] Local database is gigantic Created: 28/Jan/14 Updated: 16/Nov/21 Resolved: 21/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Daniel Rubio | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 12.04 LTS |
||
| Participants: |
| Description |
|
Hi, I need space, what can I do? Regards |
| Comments |
| Comment by Daniel Rubio [ 06/Feb/14 ] |
|
You can close the Issue. I cannot find the "Resolve button" Thx! |
| Comment by Eliot Horowitz (Inactive) [ 29/Jan/14 ] |
|
The local database is always excluded from the backup service, so won't cost anything. |
| Comment by Daniel Rubio [ 28/Jan/14 ] |
|
That's the reason why I have 1.111h available in the Replica Chart on MMS service, isn`t it?? https://mms.mongodb.com/chart/bookmark/510446077fe227e9f1832ec9/52e7b1b8e4b09932cfa67209 Oplog is stored into local "database". Do you recommend me to exclude it from Backup service?? Regards |
| Comment by Sergei Tulentsev [ 28/Jan/14 ] |
|
http://docs.mongodb.org/manual/tutorial/change-oplog-size/ Large oplog is useful when secondaries may go offline for periods of time. The bigger it is, the longer secondary can stay offline and receive incremental update afterwards. I leave it up to you to calculate more appropriate size for your case. |
| Comment by Daniel Rubio [ 28/Jan/14 ] |
|
I have the default options and my disk in 2TB, that's the reason (I guess). How can I change that size?? What size do you recommend me?? Regards and thanks |
| Comment by Sergei Tulentsev [ 28/Jan/14 ] |
|
What's the size of your oplog (defaults to 5% of disk size, IIRC)? Maybe make it smaller? |