[SERVER-81195] InvalidOptions error should be handled as any other unexpected error in the CatalogCache Created: 19/Sep/23  Updated: 29/Oct/23  Resolved: 26/Sep/23

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Aitor Esteve Alvarado
Resolution: Fixed Votes: 0
Labels: car-71-backport-declined, neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-10-02
Participants:

 Description   

The goal of this task is to remove this catch-stmt from the CatalogCache.  This catch-stmt was introduced in SERVER-57380, trying to provide better loggings for customers that were not following the standard upgrade/downgrade procedures: more specifically, they were not replacing the binaries in the proper order.



 Comments   
Comment by Githook User [ 22/Sep/23 ]

Author:

{'name': 'Aitor Esteve Alvarado', 'email': 'aitor.esteve@mongodb.com', 'username': 'atesteve'}

Message: SERVER-81195 Remove InvalidOptions special treatment
Branch: master
https://github.com/mongodb/mongo/commit/216ec9046617a52338363a409caec0b3c770d033

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