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

Does not set arbiterOnly:true if journal enabled

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major - P3 Major - P3
    • None
    • 2.6.7
    • Replication, Usability
    • None
    • ALL

    Description

      Made mistake in arbiter configuration, did
      'storage.journal.enabled' instad of 'journal.enabled', and then
      rs.addArb(myhost);
      arbiter became PRIMARY, as its beign hosted on most powerful server.

      cleared /data/arb directory and disabled journaling, and all worked as expected

      mongo 2.6.7

      Attachments

        Activity

          People

            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            drontxl@yandex.ru Andrew Grachov
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: