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

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

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.3.11
    • Sharding
    • None
    • Fully Compatible
    • Sharding 18 (08/05/16)

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              esha.maharishi@mongodb.com Esha Maharishi
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: