-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2024-02-19
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The current ClusterRole API exposes a set of very open and generic functions that don't auto-describe the real use causes that the callers want to achieve.
In order to improve the readability of the code, the idea is to expose an API with clear function names that better descrive what they do.
The instances of this class model the role (or roles) of the current process (node) that is actually a member of a sharded cluster. If the process is a standalone or a replica set member, then there is no cluster role.
An draft idea is to have an API that looks as follows:
- isRouterOnly
- isRouter
- isShardOnly
- isShard
- duplicates
-
SERVER-79545 Improve ClusterRole class
-
- Backlog
-
- is depended on by
-
-
- Closed
-
- related to
-
-
- Blocked
-
-
-
- Closed
-
-
-
- Backlog
-