[SERVER-21519] Mongodb enable oplog not working Created: 18/Nov/15  Updated: 03/Dec/15  Resolved: 02/Dec/15

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: j smith Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I have a standalone instance of mongodb (on windows) and want to enable oplog without replicaset.

I set the --master option in my windows service path. But oplog is not getting created. Any advice?

D:\MongoDB\2.6.5\bin\mongod.exe --dbpath=D:\MongoDB\2.6.5\data\db\ --logpath=D:\MongoDB\2.6.5\log\mongo.log --service --master

MongoDB version 2.6.5



 Comments   
Comment by Kelsey Schubert [ 02/Dec/15 ]

Hi jsmithap,

I noticed that you are using atypical command line options:

  • --master will create local.oplog.$main (for the legacy master/slave set up). I would recommend using --replSet and initializing it as a 1-node replica, which will create the expected local.oplog.rs
  • --service doesn't appear to be a valid option: https://docs.mongodb.org/v2.6/reference/program/mongod.exe

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag.

Regards,
Thomas

Comment by Kelsey Schubert [ 19/Nov/15 ]

Hi jsmithap,

I haven't been able to reproduce this issue. Can you please provide the mongo.log during the startup process?

Thank you,
Thomas

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