[SERVER-1072] The --oplogSize command line switch is silently ignored unless the local.* database files have been removed Created: 01/May/10  Updated: 12/Jul/16  Resolved: 10/May/10

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 1.4.1
Fix Version/s: 1.5.2

Type: Improvement Priority: Minor - P4
Reporter: Chuck Remes Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OSX 10.6.3, mongod 1.4.1 64-bit


Backwards Compatibility: Minor Change
Participants:

 Description   

The --oplogSize command line switch is ignored by the mongod server if local.* database files already exist. The only way change the size of the oplog is to manually remove those files and restart the server daemon.

I suggest that, at minimum, a warning should be printed to the mongod logfile indicating that the --oplogSize switch was ignored when local.* files already exist. A pointer to the docs would be a "nice to have."



 Comments   
Comment by auto [ 10/May/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: docs for SERVER-1072
http://github.com/mongodb/mongo/commit/4a40ae3a34b864d9ea8e8d7a7b50341f413ddc7d

Comment by auto [ 10/May/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: don't start when a oplog size is requested different than exists SERVER-1072
http://github.com/mongodb/mongo/commit/7ff25dc9755397027046b91bf6667be6f46759d0

Generated at Thu Feb 08 02:55:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.