[DOCS-11650] Make clear that oplog size limit is BSON not storage size at /manual/core/replica-set-oplog/#oplog-size Created: 24/Apr/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Nic Cottrell | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
This page doesn't make clear that the oplog size we set is actually the document size and not the storage size (like I believe it was in MMAP?). So we should expect that the actual storage size on disk would be a fraction of this oplog size. This might be important information for customers (like mine) who will need an oplog of about 60GB of documents (uncompressed) but which actually takes only 15GB on disk. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |