Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10011

Using configsvr sets oplogSize explicitly causing errors

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Gone away
    • Affects Version/s: 2.4.0
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
    • Operating System:
      ALL

      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

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            scotthernandez Scott Hernandez
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: