[SERVER-63530] TTL Monitor should not log an error message on StaleShardVersion errors Created: 10/Feb/22  Updated: 29/Oct/23  Resolved: 11/Feb/22

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

Type: Bug 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
Duplicate
is duplicated by SERVER-63529 TTL Monitor should not log an error m... Closed
Problem/Incident
is caused by SERVER-63245 TTL Monitor thread doesn't recover th... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-02-21
Participants:
Linked BF Score: 135

 Description   

We should lower the error level for StaleShardVersion errors on the TTL Monitor because:

  • We can recover from it: next time that TTL task is executed it will probably succeed: as part of the error handling we trigger a refresh of the shard filtering information.
  • We have other tools in our pipeline looking for errors.


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

Author:

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

Message: SERVER-63530 Lowering error level of TTL tasks that fail on SSV
Branch: master
https://github.com/mongodb/mongo/commit/bf11296b533b07bd4b87f64e7477cc147c7697ea

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