Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: 6.1.1, 4.2.24, 4.4.19, 5.0.15, 6.0.4, 6.2.0-rc0
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0, 6.1.0-rc3
Component/s: Sharding
Labels:
- sharding-nyc-subteam1

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.1, v6.0, v5.0, v4.4, v4.2
Sprint:
Sharding 2022-08-08, Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19, Sharding NYC 2022-11-14
Linked BF Score:
113
Story Points:
5
Confidence Status:
None
Work Order:
0
CAR Domain/s:
None

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

Original summary

Investigate getPreImageDocumentKey calls in LogTransactionOperationsForShardingHandler::commit

Original description

It is called a few times around here:
https://github.com/mongodb/mongo/blob/119e6b5979e4b1e8fcf91db711673393c56b4020/src/mongo/db/s/migration_chunk_cloner_source_legacy.cpp#L240

But there appears to be no code setting the value.

is caused by

SERVER-39940 Model a shard key update as a delete inside the chunk migration cloner if the document moves out of a currently-migrating chunk

Closed

is related to

SERVER-40791 Chunk migration clone blocks behind prepared transactions

Closed

SERVER-71028 MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict

Backlog

related to

SERVER-71219 Migration can miss writes from prepared transactions

Closed

SERVER-70152 PeekableCursor's definition of hasNext() ignores the state of the stashed document

Closed

Assignee:: Randolph Tan
Reporter:: Randolph Tan
Participants:: Githook User, Max Hirschhorn, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jul 27 2022 05:55:40 PM UTC
Updated:: Oct 29 2023 09:35:15 PM UTC
Resolved:: Nov 10 2022 02:47:42 PM UTC
Confidence Status Last Update:: 03/Nov/22 4:22 PM