[SERVER-36004] SessionUpdateTracker should ignore no-op entries for pre/post image oplogs Created: 06/Jul/18  Updated: 29/Oct/23  Resolved: 26/Feb/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.13, 4.1.9, 4.0.11

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-31769 Retrying findAndModify can error if o... Closed
Related
related to SERVER-31769 Retrying findAndModify can error if o... Closed
related to SERVER-67492 Failed chunk migrations can lead reci... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: Sharding 2019-03-11
Participants:
Linked BF Score: 13

 Description   

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.



 Comments   
Comment by Githook User [ 04/Jun/19 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-36004 SessionUpdateTracker should ignore no-op entries for pre/post image oplogs

(cherry picked from commit 9638317daa5300efdd43acfa4688e5c739beff4d)
(cherry picked from commit 39f932b0a4f580f7c9dcefb8b3a47335fdb4539f)
Branch: v3.6
https://github.com/mongodb/mongo/commit/0c2e3a6b1ea226c9dfb9822b57f02399950493dc

Comment by Githook User [ 04/Jun/19 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-36004 SessionUpdateTracker should ignore no-op entries for pre/post image oplogs

(cherry picked from commit 9638317daa5300efdd43acfa4688e5c739beff4d)
Branch: v4.0
https://github.com/mongodb/mongo/commit/39f932b0a4f580f7c9dcefb8b3a47335fdb4539f

Comment by Githook User [ 26/Feb/19 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-36004 SessionUpdateTracker should ignore no-op entries for pre/post image oplogs
Branch: master
https://github.com/mongodb/mongo/commit/9638317daa5300efdd43acfa4688e5c739beff4d

Comment by Randolph Tan [ 28/Jan/19 ]

kaloian.manassiev I think it can be done in a day

Comment by Kaloian Manassiev [ 28/Jan/19 ]

renctan, is this about 1 day of work? Also do you mind updating the description with what is the side effect of this bug - it is kind of difficult to gauge.

Generated at Thu Feb 08 04:41:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.