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

harden checks around using --shardSvr, --overrideShardIdentity, and queryableBackupMode

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 18 (08/05/16)

      in queryableBackupMode:

      • require --overrideShardIdentity if started with --shardsvr
      • add a warning if started with --overrideShardIdentity but not --shardsvr

      in non-queryableBackupMode:

      • fail if started with --overrideShardIdentity
      • add a warning if a shardIdentity document exists on disk but not started with --shardsvr
      • add a warning if no shardIdentity document exists on disk but started with --shardsvr

      additionally:

      • use Date_t::max() as the deadline for initializeFromShardIdentity() in all cases
      • generally refactor startup and shard aware initialization code for clarity and conciseness

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: