[SERVER-47336] Only reset stale shards under catalog cache mutex when returning back a same-version routing history Created: 03/Apr/20  Updated: 29/Oct/23  Resolved: 10/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc2, 4.7.0

Type: Bug 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:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-04-20
Participants:
Linked BF Score: 25

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

Author:

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

Message: SERVER-47336 Reset stale shards under catalog cache mutex when returning back the same routing history

(cherry picked from commit 8ebe78a87142137172358290b9da6551db3ae322)
Branch: v4.4
https://github.com/mongodb/mongo/commit/c3a6d6aa8004ead83aaf0687b19469bba449b452

Comment by Githook User [ 06/Apr/20 ]

Author:

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

Message: SERVER-47336 Reset stale shards under catalog cache mutex when returning back the same routing history
Branch: master
https://github.com/mongodb/mongo/commit/8ebe78a87142137172358290b9da6551db3ae322

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