Check accessing sharded cluster components on replicasets running with --shardsvr

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      In transitioning_replica_sets_jscore_passthrough suite we run a replicaset started as --shardsvr but not part of a cluster. This transition state is valid, and we should be able to execute commands.

      The failing test is jstests/core/query/internal_rename_if_options_and_indexes_match.js which is doing an internalRenameIfOptionsAndIndexesMatch.

      The task is to figure out if we can run these type of commands (accessing sharding state if running with --shardsvr) somehow during the transitional phase

      Investigate too if the ShardingStateNotInitialized exception can be removed from sharded_cluster_util.py

            Assignee:
            Unassigned
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: