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

Service, Logs, FTDC and Metrics should not rely on the ClusterRole API

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability

      Today, Service, Logs, FTDC, and Metrics re-use the public enum provided by the ClusterRole.

      These components only use the values ShardServer, RouterServer and None from the enum and not the bit mask of the ClusterRole class, making more harder to use and unnecessary calls to hasExclusively and extras MONGO_UNREACHABLE.

      The goal of this ticket is to make all those components depend on a new enumeration with three values Shard, Router and None in order to break the relationship with the ClusterRole API.

            Assignee:
            Unassigned Unassigned
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: