[SERVER-53301] Always throw StaleEpoch with namespace extra info Created: 09/Dec/20  Updated: 14/Oct/21  Resolved: 14/Oct/21

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Won't Do Votes: 0
Labels: 5.0-cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding EMEA 2021-11-15
Participants:

 Description   

SERVER-52631 has associated an optional StaleEpochInfo to the StaleEpoch error.

Once 5.0 is released, it will be possible to always attach the extra info when throwing such exception since all subsequent versions will be able to parse it.

(Currently, v4.4 doesn't expect SlaleEpoch to have extraInfo, so multiversion support would not be achievable)



 Comments   
Comment by Pierlauro Sciarelli [ 14/Oct/21 ]

Closing because we'll try to replace all the occurrences of StaleEpoch with StaleConfig

Comment by Kaloian Manassiev [ 09/Dec/20 ]

Ideally, we shouldn't throw StaleEpoch at all and should be using StaleConfigInfo as the single exception which is used to drive the "clock" of the collection/shardVersion.

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