[SERVER-74673] Add specific coordinator attributes in ShardingDDLCoordinator logs. Created: 07/Mar/23  Updated: 13/Dec/23  Resolved: 13/Dec/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: car-qw, oldshardingemea, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25
Participants:
Story Points: 1

 Description   

The logs emitted by ShardingDDLCoordinator infrastructure (e.g. retry, error, ...) only contains the coordinator ID.

Many coordinators contains specific parameters that could help in the debugging process, for instance when a movePrimary fails it would be useful to know also which was the destination shard.

We could achieve by exposing a function similar to appendComamndInfo that instead of appending to a BSONObjBuilder appends elements to a mongo::logv2::DynamicAttributes.



 Comments   
Comment by Githook User [ 12/Dec/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-74673 Add method for logging custom attributes per coordinator

GitOrigin-RevId: 856a8e09077d1ec03df494ddbf8668fc3a9ea68f
Branch: master
https://github.com/mongodb/mongo/commit/c000a44c11540f4357dded30e8a61844f4c0ab6a

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