[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:

<dt> [initandlisten] cmdline oplogsize (5) different than existing (10) see: http://dochub.mongodb.org/core/increase-oplog



 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.

Generated at Thu Feb 08 03:22:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.