[SERVER-60144] Handle stale routing info on mongos for sharded time-series collections Created: 22/Sep/21  Updated: 29/Oct/23  Resolved: 30/Sep/21

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

Type: Bug Priority: Major - P3
Reporter: Nikita Lapkov (Inactive) Assignee: Arun Banala
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-60308 Test deletes in the presence of stale... Closed
Duplicate
duplicates SERVER-59810 mongos may see the timeseries collect... Closed
Problem/Incident
causes SERVER-78997 Recreating a sharded timeseries colle... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QE 2021-10-04
Participants:

 Comments   
Comment by Githook User [ 19/Oct/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-60144 Handle stale routing info on mongos for sharded time-series collections

(cherry picked from commit 5e0dffb6d2723470e1f1bd93de6565c7a4e0353a)
Branch: v5.0
https://github.com/mongodb/mongo/commit/86fd08c31ebbb108412e7202e79017626a031227

Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 30/Sep/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-60144 Handle stale routing info on mongos for sharded time-series collections
Branch: master
https://github.com/mongodb/mongo/commit/5e0dffb6d2723470e1f1bd93de6565c7a4e0353a

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