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

Require --shardsvrs not started in queryable backup mode to be started as replica sets

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.1 Desired
    • Component/s: Sharding
    • Labels:
      None

      Description

      A commit to require --shardsvrs to be started as replica sets under SERVER-32105 went into 3.6.1, but was reverted because mongods started in queryable backup mode cannot be started as replica sets.

      This ticket should re-commit the original patch, but allowing an --shardsvrs in queryable backup mode to be started as standalone servers.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-6621 mongos doesn't learn if a shard becomes a replica set after the mongos started up

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32529 Requiring replSet for shards breaks Queryable Backup

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34121 "Cannot specify afterClusterTime readConcern without replication enabled"

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-32052 Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-32105 Require shard servers and config servers to be started with --replSet or 'replSetName'

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated: