[SERVER-52784] Retry command on stale exception on shards only if the shard is stale Created: 11/Nov/20  Updated: 06/Dec/22  Resolved: 23/Mar/21

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-53000 Retry command on stale exception on s... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Thanks to  SERVER-28943 shards now retry non-write commands on stale exception.
This is done unconditionally even if the exception is indicating that the router was stale.

Once database and collection version will be truly comparable (SERVER-52587) we can conditionally refresh and retry the command only if "requiredVersion (Router) > wantedVersion (Shard)".

This new behavior should be either addressed once 5.0 becomes last-lts or should be guarded by an FCV flag in order to be sure that we are on a binary version that uses truly comparable database and collection versions.



 Comments   
Comment by Ratika Gandhi [ 20/Nov/20 ]

It is a nice idea but not a high priority right now.

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