Consolidate uses of ClusterRole and ShardingState::enabled()

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      To conditionally run code on a shard, we often use both serverGlobalParams.clusterRole == ClusterRole::ShardServer and ShardingState::enabled(). Instead, we should use the cluster role checks for startup logic (since it's set by a command line option) and ShardingState everywhere else.

            Assignee:
            [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: