Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0-rc7, 4.7.0
Affects Version/s: None
Component/s: Replication, Storage
Labels:
None

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

v4.4, v4.2
Sprint:
Repl 2020-05-18
Linked BF Score:
50

~~SERVER-41766~~ changed the catalog multikey update for multi-statement transactions on primaries to happen in a side transaction. This side transaction looks at the logical clock to find a timestamp far enough in the future to use for writing to the catalog.

Because (I believe) we only perform this ghost timestamp on primaries, it's preferable to instead write a no-op oplog entry. That way the stable timestamp never races with the transaction being committed. Durable history may have different consequences due to these races.

is related to

SERVER-42251 Cannot timestamp multikey write during recovery of prepared transaction before LogicalClock has been initialized

Closed

SERVER-46229 setting multikey on index fails if index was created within same multi-document transaction

Closed

SERVER-49949 Reconstructing prepared transactions containing multi-key writes crashes the initial syncing node.

Closed

SERVER-47867 Remove ghost timestamping code

Closed

SERVER-48024 Have validate compare collection object with on-disk metadata object

Closed

related to

SERVER-48465 restore noop write msg format for single-phase index builds

Closed

(1 related to)

Assignee:: Judah Schvimer

Reporter:: Daniel Gottlieb (Inactive)

Participants:: Daniel Gottlieb, Githook User, Judah Schvimer, Tess Avitabile

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: May 07 2020 03:43:57 PM UTC

Updated:: Oct 29 2023 10:08:34 PM UTC

Resolved:: May 12 2020 12:34:58 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates