[SERVER-59061] Shard does not block inserts into time-series collection when in critical section Created: 03/Aug/21  Updated: 13/Oct/21  Resolved: 26/Aug/21

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

Type: Bug Priority: Major - P3
Reporter: Nikita Lapkov (Inactive) Assignee: Nikita Lapkov (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-57567 Update sharded passthrough suite to h... Closed
is depended on by SERVER-59155 Enable some of the time-series tests ... Closed
Related
related to SERVER-59164 All write commands on sharded time-se... Closed
is related to SERVER-59164 All write commands on sharded time-se... Closed
Operating System: ALL
Backport Requested:
v5.0
Sprint: QE 2021-08-09, QE 2021-08-23, QE 2021-09-06
Participants:

 Description   

One of the steps during chunk migration is a critical section. While in critical section, shard should not accept any writes to the collection.

While this is true for normal collection, for some reason time-series collection does accept writes during critical section. This could potentially lead to data loss, since the migrated chunk will be eventually deleted from the destination shard.


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