[SERVER-44972] [finer-grained ssv] Strengthen invariants for StaleConfigException shard IDs after branching for 4.5 Created: 05/Dec/19  Updated: 29/Oct/23  Resolved: 15/Apr/20

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-04-06, Sharding 2020-04-20
Participants:

 Description   

Currently, it's possible for StaleConfigExceptions to not contain a shard's ID dependent of the binary version of the node in the cluster. After the branch, we should do the following:

  1. Source all places where a StaleConfigException is caught and fassert that the shard's ID exists.
  2. Remove all conditional logic that allow for a shard ID to not exist in a StaleConfigException when taking action on a stale shard.

 



 Comments   
Comment by Githook User [ 15/Apr/20 ]

Author:

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

Message: SERVER-44972 Make ShardId a required field in StaleConfigInfo
Branch: master
https://github.com/mongodb/mongo/commit/2c87953010c2c1ec2d39dc9a7dbbd5f7d49dab10

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