Using configsvr sets oplogSize explicitly causing errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.4.0
    • Component/s: Sharding
    • Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: