Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.3.0
Affects Version/s: None
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Linked BF Score:
35
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

causes

SERVER-63530 TTL Monitor should not log an error message on StaleShardVersion errors

Closed

SERVER-63567 Flag the ttl_monitor_recovers_shard_version.js with the requires_persistence flag

Closed

is caused by

SERVER-61847 Handle direct updates/deletes to shards that modify orphan docs

Closed

related to

SERVER-58036 TTL monitor can delete documents during chunk migration's and resharding's critical sections

Closed

Assignee:: Sergi Mateo Bellido
Reporter:: Sergi Mateo Bellido
Participants:: Githook User, Sergi Mateo Bellido
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Feb 03 2022 01:06:52 PM UTC
Updated:: Oct 29 2023 09:43:11 PM UTC
Resolved:: Feb 08 2022 06:52:04 AM UTC
Confidence Status Last Update:: 03/Feb/22 1:16 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates