[SERVER-20912] rs.initiate allows the creation of a non-capped oplog Created: 14/Oct/15 Updated: 06/Dec/22 Resolved: 28/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.7, 3.1.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | Start a member with --replSet foo
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, if you create the local.oplog.rs collection prior to running rs.initiate, you can create a replset that has an unbounded oplog. Ideally we should either prevent this, alert (and potentially fail) when running rs.initiate() and a non-capped oplog.rs is found. And potentially have a preflight check when starting as a repl member, then alerting and hanging until a resolution is found. |
| Comments |
| Comment by Michael Cahill (Inactive) [ 28/Oct/15 ] |
|
dup of |