Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.2.0
Affects Version/s: None
Component/s: None
Labels:
None

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

v5.0
Sprint:
Execution Team 2021-11-15, Execution Team 2021-11-29
Linked BF Score:
152

Using dupsAllowed=false when inserting into a secondary unique index results in inserting + removing on a "prefix" document to serialize access to enforce unique constraints.

However the preceding comment states the expectation that only primaries are executing that code path.

This results in unnecessary writes to these prefix documents. Moreover, these writes can result in out of order update chains as secondaries can process oplog entries out of order.

depends on

SERVER-61459 ShardingCatalogManager::assignKeyRangeToZone() reads stale version of CollectionType while running locally on config server primary

Closed

is duplicated by

SERVER-60716 Remove out of order writes on unique, non _id indexes

Closed

is related to

SERVER-60037 Enable the ordered timestamp assertion in MongoDB

Closed

related to

SERVER-61458 Calling RSLocalClient::queryOnce(kMajorityReadConcern) causes subsequent local writes in same OperationContext to also read stale data

Closed

SERVER-61499 Complete TODO listed in SERVER-60716

Closed

WT-7853 Validate the update chain before we attempt to insert it into the history store

Closed

(1 related to)

Assignee:: Yuhong Zhang

Reporter:: Daniel Gottlieb (Inactive)

Participants:: Daniel Gottlieb, Githook User, Louis Williams, Yuhong Zhang

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: Sep 08 2021 02:42:07 AM UTC

Updated:: Jul 16 2024 05:11:45 PM UTC

Resolved:: Nov 19 2021 02:48:16 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates