[SERVER-63245] TTL Monitor thread doesn't recover the shard version Created: 03/Feb/22  Updated: 29/Oct/23  Resolved: 08/Feb/22

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-63530 TTL Monitor should not log an error m... Closed
causes SERVER-63567 Flag the ttl_monitor_recovers_shard_v... Closed
is caused by SERVER-61847 Handle direct updates/deletes to shar... Closed
Related
related to SERVER-58036 TTL monitor can delete documents duri... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Participants:
Linked BF Score: 35

 Description   

Direct deletes to a shard might throw an StaleShardVersion exception (introduced in SERVER-61847). Under that scenario, the TTL Monitor logs an error but it doesn't recover the shard version. Thus, if there are no other operations, the next time that TTL task is executed it will also fail.



 Comments   
Comment by Githook User [ 08/Feb/22 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-63245 Handling StaleShardVersion error for TTL Indexes
Branch: master
https://github.com/mongodb/mongo/commit/1c975d64aa2c60da302a4dab26e7ec1b792d8740

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