Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2023-08-07
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

TimeseriesModifyStage is affected by the same issues described on ~~SERVER-77116~~ and ~~SERVER-78470~~. On sharded deployments, in the presence of concurrent chunk migrations, this can cause an updateOne write to be executed twice.

related to

SERVER-77116 Checking shard version during restore can cause StaleConfig exception propagated for writes incorrectly

Closed

SERVER-78470 Prevent multi-false UpdateStage/DeleteStage from provoking yield after having already written

Closed

SERVER-91771 Reduce code duplication for StaleConfig handling within update and delete related PlanStages

Backlog

Assignee:: Jordi Serra Torrens
Reporter:: Jordi Serra Torrens
Participants:: Githook User, Jordi Serra Torrens
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 27 2023 02:16:22 PM UTC
Updated:: Jun 21 2024 11:06:24 PM UTC
Resolved:: Jul 28 2023 07:28:56 AM UTC
Confidence Status Last Update:: 27/Jul/23 2:19 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates