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

Extend roles that a cluster node can act with router

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • Sharding
    • None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-07-10

    Description

      When a MongoD process is part of a cluster, it can act (inclusively) as shard, config and now also as a router.

      The actual process role is stored in the clusterRole global parameter, which can only assume the none, shard and config roles.

      The goal of this ticket is to include the router role to the ClusterRole class and allow the non-exclusivity of roles. In this way the clusterRole global parameter can model MongoD processes configured to act as shard only, shard + router or router only.

      Attachments

        Activity

          People

            antonio.fuschetto@mongodb.com Antonio Fuschetto
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: