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

Support for configServer labeling of replica set configurations

    • Type: Icon: New Feature New Feature
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 7 08/10/15, Sharding 8 08/28/15

      Replica set configs for CSRS must have a top level field configServer set to boolean true.

      A node should enter the REMOVED state and otherwise behave as though it was not listed in a replica set config if any of the following hold:

      1. If the node is started with --configsvr and its replica set configuration does not have configsvr: true;
      2. If a node is started without --configsvr and its replica set configuration does have configsvr:true;
      3. If a node is started with --configsvr and its configuration does have configsvr:true and its storage engine is not wired tiger and it does not have --configsvrMode=sccc

      Replica sets with the configsvr: true flag should reject configurations that contain arbiters.

      Sets with configServer: true in their config must return a top level configsvr: true field in their response to replSetGetStatus.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            schwerin@mongodb.com Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: