[SERVER-44587] Modify StaleConfigInfo to take in and store a shard's ID. Created: 12/Nov/19  Updated: 29/Oct/23  Resolved: 06/Jan/20

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-44500 Create a new ShardVersionMap that inc... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 06/Jan/20 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-44587 Modify StaleConfigInfo to take in and store a shard's ID
Branch: master
https://github.com/mongodb/mongo/commit/ee418d7af4e499a950bbf4b90eca4fed1b08474a

Comment by Mira Carey [ 12/Nov/19 ]

I think this is the right kind of idea, but I'm not sure if ExtraErrorInfo is exactly what you want here.

ErrorExtraInfo is a mandatory sidecar for particular error codes. I.e. CommandOnShardedViewNotSupportedOnMongod always requires its resolved view.

It isn't useful for attaching optional metadata for arbitrary exception types.

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