[SERVER-49917] allow to resize capped collections Created: 26/Jul/20 Updated: 18/Sep/20 Resolved: 18/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.19, 3.6.19, 4.2.8 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Kay Agahd | Assignee: | Michael Gargiulo |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Execution Team 2020-08-24, Execution Team 2020-09-07, Execution Team 2020-09-21 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Since mongodb version 3.6 it is possible to resize the oplog, which is a capped collection. This feature is even more important as long as capped collections cannot be created by defining the maximal "storageSize" (see |
| Comments |
| Comment by Michael Gargiulo [ 18/Sep/20 ] |
|
See comments for the explanation for closing as "Won't Do" in |
| Comment by Kay Agahd [ 06/Aug/20 ] |
|
Hi Dima, I just wrote in our techblog how we worked around the issue that capped collections cannot be resized without downtime so far: |
| Comment by Dmitry Agranat [ 28/Jul/20 ] |
|
Oplog is a special capped collection so your mention of Oplog with other capped collection was a bit confusing. Thanks for clarifying this point. Thanks, |
| Comment by Kay Agahd [ 27/Jul/20 ] |
|
Hi Dima, I meant that it's possible to resize the oplog since mongodb version 3.6. Older mongodb versions did not have the replSetResizeOplog command. |
| Comment by Dmitry Agranat [ 27/Jul/20 ] |
|
Given our documentation for Oplog resize, could you please clarify what do you mean by:
Thanks, |