Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.13, 4.1.9, 4.0.11
Affects Version/s: None
Component/s: Sharding
Labels:
- sharding-wfbf-day

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

v4.0, v3.6
Sprint:
Sharding 2019-03-11
Linked BF Score:
13
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

These pre/post entries is only valid if paired with the corresponding update/delete oplog entries. Since the update/delete oplog entry always comes after the pre/post entry and both of these entries contain the same amount information necessary to properly replicate the config.transactions table, the pre/post entry should be ignored. Otherwise, it can create a situation where the secondary replication would mistakenly think that write was performed if sees the pre/post entry even though the update/delete oplog entry was removed due to replication rollback.

Note: it should not ignore no-op entries generated during session migration.

is duplicated by

SERVER-31769 Retrying findAndModify can error if oplog write for was rolled back

Closed

related to

SERVER-31769 Retrying findAndModify can error if oplog write for was rolled back

Closed

SERVER-67492 Failed chunk migrations can lead recipient shard to have divergent config.transactions records between primary and secondaries

Closed

Assignee:: Randolph Tan
Reporter:: Randolph Tan
Participants:: Githook User, Kaloian Manassiev, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 06 2018 09:58:22 PM UTC
Updated:: Oct 29 2023 10:30:04 PM UTC
Resolved:: Feb 26 2019 09:02:56 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates