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

re-enable read_only_sharded suite

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • Sharding 2016-08-29, Sharding 2016-10-31

      Because these tests restart a shard in queryableBackupMode, they must provide the shardIdentity document for the restarted shard to use through the overrideShardIdentity startup parameter.

      However, this parameter must be passed through a yaml configuration file (by design).

      Since the shardIdentity document must contain a valid config connection string, we need to add a workaround to either:

      1) be able to know before-hand what the config connection string will be, and create a dummy yaml config file in jstests/libs, OR
      2) somehow determine the config connection string at runtime and write it to a config yaml file through the javascript helpers for running bash commands (will work for linux-only)

      and point the restarted shard to the yaml config file.

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            0 Vote for this issue
            4 Start watching this issue