[SERVER-10011] Using configsvr sets oplogSize explicitly causing errors Created: 24/Jun/13 Updated: 06/Dec/22 Resolved: 20/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | configsvr, oplog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
If you increase the oplog then after restarting the server, without any oplog size, or different than the current size, it will give this error:
|
| Comments |
| Comment by Esha Maharishi (Inactive) [ 20/Jul/18 ] |
|
Starting in 3.4 SCCC is no longer supported, which means you can't start config servers not as replica set. |