Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.0.0-rc6, 6.1.0-rc0
Affects Version/s: None
Component/s: Replication, Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.0
Sprint:
Sharding EMEA 2022-05-02, Sharding EMEA 2022-05-16
Linked BF Score:
135
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

The full picture of problem and solution is described here.

The goal of this ticket is to extend the applyOps entries with the fromMigrate flag and set it when the operations involve orphaned documents.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

7fd37fc0.png
May 02 2022 08:01:48 AM UTC
71 kB
Antonio Fuschetto
abfd8588.jpg
May 02 2022 08:04:54 AM UTC
53 kB
Antonio Fuschetto

causes

SERVER-67352 Skip identifying writes on orphaned documents in replica set deployments

Closed

is depended on by

SERVER-65859 Enable filtering of change steam events for individual statements of transactions

Closed

SERVER-64107 Clean up orphaned doc handling in the batched deleter

Closed

SERVER-65295 Handle direct CRUD ops to shards as part of a txn introducing orphan documents

Closed

related to

SERVER-66312 Tests on batched operations do not involve orphaned documents

Closed

SERVER-66423 Set the fromMigrate flag of DurableReplOperation entries only when FCV is 6.0 or greater

Closed

SERVER-74589 move logic for marking orphan documents out of logOplogInserts

Closed

(2 related to)

Assignee:: Antonio Fuschetto
Reporter:: Antonio Fuschetto
Participants:: Antonio Fuschetto, Githook User
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Apr 21 2022 07:53:47 AM UTC
Updated:: May 20 2025 10:03:50 PM UTC
Resolved:: May 06 2022 03:42:05 PM UTC
Confidence Status Last Update:: 21/Apr/22 8:12 AM