[SERVER-36411] Changelog entries should include shard name Created: 02/Aug/18  Updated: 29/Oct/23  Resolved: 14/Nov/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-35639 Changelog entries should include port Closed
related to SERVER-49307 In changelog, report the shard name (... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-09-24, Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19
Participants:

 Description   

SERVER-35639 added the port to the hostname in changelog entries. However, if the replset membership of shards is changing frequently, it can still be hard to match up this host:port with the corresponding shard, eg. if a config dump from the appropriate time is not available (since the entries in config.shards are not versioned). Therefore, it would be useful if changelog entries also included an optional field which is the name of the shard performing the operation (for operations on shards), "config" for operations on configsvrs, and absent for operations on mongos.



 Comments   
Comment by Githook User [ 14/Nov/18 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-36411 include shard id/name in changelog/actionlog entries
Branch: master
https://github.com/mongodb/mongo/commit/c2cc425b9d2b23eead06ecbfd996375e47c81baa

Generated at Thu Feb 08 04:43:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.