[SERVER-74459] Reword shard identity startup logs to apply to a config server Created: 28/Feb/23  Updated: 29/Oct/23  Resolved: 24/Mar/23

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

Type: Improvement Priority: Major - P3
Reporter: Jack Mulrow Assignee: Wenqin Ye
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-03-06, Sharding NYC 2023-03-20, Sharding NYC 2023-04-03
Participants:

 Description   

When starting up a mongod with the shard server role, we check for the existence of a shard identity document on disk. If we cannot find it, we log:

 "Started with --shardsvr, but no shardIdentity document was found on disk. This most likely means this server has not yet been added to a sharded cluster"

Now that a config server will always have the shard role, it's not accurate to say "started with --shardsvr." We should reword the log to be less specific to the particular command line option and instead say something like "Started with shard role, but ..." and exclude the "This most likely means" sentence on a config server, since the config server will insert its own shard identity document on first step up to primary.



 Comments   
Comment by Githook User [ 23/Mar/23 ]

Author:

{'name': 'wenqinYe', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-74459: Reword shard identity startup logs to apply to a config server
Branch: master
https://github.com/mongodb/mongo/commit/e53b04273cff9eb526d61ae77a3a5f2ddec95f9e

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