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

re-enable read_only_sharded suite

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.0-rc2
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2016-08-29, Sharding 2016-10-31

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              esha.maharishi Esha Maharishi
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: