[SERVER-60143] Avoid clearing filtering metadata after failed metadata refresh Created: 22/Sep/21  Updated: 29/Oct/23  Resolved: 18/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0, 5.0.14

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-11-01
Participants:

 Description   

This clearFilteringMetadata after a failed refresh shouldn't be necessary. In that situation, the exception is already propagated to the caller of onShardVersionMismatch. Moreover, on the following requests that do shardVersion checking, onShardVersion mismatch should already be called anyway if the metadata was unknown/stale; so there should not be a need to explicitly clear the filtering metadata.



 Comments   
Comment by Githook User [ 04/Nov/22 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-60143 Avoid clearing filtering metadata after failed metadata refresh

(cherry picked from commit d517aaef938089d0d5500a6722db53109d4d9965)
Branch: v5.0
https://github.com/mongodb/mongo/commit/fd12dbc77432dd01ee37a9655d6657d9f9f9afa0

Comment by Githook User [ 18/Oct/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-60143 Avoid clearing filtering metadata after failed metadata refresh
Branch: master
https://github.com/mongodb/mongo/commit/d517aaef938089d0d5500a6722db53109d4d9965

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