[SERVER-82469] The `serverStatus` command incorrectly returns that a server config always acts as shard Created: 26/Oct/23  Updated: 07/Nov/23  Resolved: 07/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-81231 Extend the `serverStatus` command to ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-10-30, CAR Team 2023-11-13
Participants:

 Description   

After SERVER-81231, the output of the serverStatus command reports the sharding.clusterRoles key containing the list of roles actually acted by the node (e.g., router, shard, config).

This new key reflects the actual configuration of the process (ClusterRole). Unfortunately, in case of a config server, the node apparently acts a shard, so the serverStatus command returns incorrect information.

Determining whether a shard also acts as a config server is relatively complex, as the status is based on a dynamic property — whether the user has executed a transition commands or not.

The original idea was to extend the serverStatus command to provide to Atlas InTel an easy way to determine whether the embedded router is enabled or not. As a consequence, the goal of this ticket is to remove the sharding.clusterRoles key and add the sharding.routerServiceEnabled key (set to true or false).



 Comments   
Comment by Githook User [ 07/Nov/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-82469 The `serverStatus` command incorrectly returns that a server config always acts as shard
Branch: master
https://github.com/mongodb/mongo/commit/e5305ee6c6f3b46d34542ce93aef170976be5996

Generated at Thu Feb 08 06:49:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.