Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Minor Change
Sprint:
Repl 2021-05-17

The changes from ~~SERVER-55305~~ will address how a retryable write statement may execute multiple times without making atClusterTime reads on the config.transactions collection correct for all readTimestamps. To prevent accidental misuse of atClusterTime reads, they should be rejected on the config.transactions collection.

Note however that resharding depends on performing an atClusterTime read on the config.transactions collection (see SERVER-55214) and will need an undocumented option (or some internal privilege way) of continuing to use atClusterTime reads on the config.transactions collection.

is related to

SERVER-55214 Resharding txn cloner can miss config.transactions entry when fetching

Closed

SERVER-55305 Retryable write may execute more than once if primary had transitioned through rollback to stable

Closed

SERVER-56631 Retryable write pre-fetch phase could miss entry from config.transactions when reading from donor secondaries

Closed

SERVER-56796 Support atClusterTime snapshot reads on config.transactions

Backlog

Assignee:: Lingzhi Deng

Reporter:: Max Hirschhorn

Participants:: Githook User, Lingzhi Deng, Max Hirschhorn

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: Mar 26 2021 11:57:30 PM UTC

Updated:: Oct 29 2023 09:55:41 PM UTC

Resolved:: May 10 2021 12:21:59 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates