[SERVER-35763] lastWriteDate field can get out of sync between repl set nodes during migration Created: 22/Jun/18  Updated: 29/Oct/23  Resolved: 27/Aug/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.6, 4.0.0-rc2, 4.1.1
Fix Version/s: 3.6.9, 4.0.4, 4.1.3

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

Issue Links:
Backports
Depends
Related
is related to SERVER-33327 Session::onMigrateCompletedOnPrimary ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: Sharding 2018-08-27, Sharding 2018-09-10
Participants:
Linked BF Score: 68

 Description   

The issue is that during migration, we might decide to not update the lastWriteDate. However, the secondary replication doesn't have this logic and it will simply use the oplog wall time to set the lastWriteDate field.



 Comments   
Comment by Githook User [ 04/Oct/18 ]

Author:

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

Message: SERVER-35763 lastWriteDate field can get out of sync between repl set nodes during migration

Revert changes to onMigrateCompletedOnPrimary to make it easier for secondary to replicate config.transactions idempotently.

(cherry picked from commit 57d007e00124d18e94c204e3968b53f83c01f1b7)
Branch: v4.0
https://github.com/mongodb/mongo/commit/da2816551c2ab0b655a7a9b9efdb73194c165c1a

Comment by Githook User [ 27/Sep/18 ]

Author:

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

Message: SERVER-35763 lastWriteDate field can get out of sync between repl set nodes during migration

Revert changes to onMigrateCompletedOnPrimary to make it easier for secondary to replicate config.transactions idempotently.

(cherry picked from commit 57d007e00124d18e94c204e3968b53f83c01f1b7)
Branch: v3.6
https://github.com/mongodb/mongo/commit/2f859b8f70cc7c78b316af87fb6342747a363314

Comment by Githook User [ 27/Aug/18 ]

Author:

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

Message: SERVER-35763 lastWriteDate field can get out of sync between repl set nodes during migration

Revert changes to onMigrateCompletedOnPrimary to make it easier for secondary to replicate config.transactions idempotently.
Branch: master
https://github.com/mongodb/mongo/commit/57d007e00124d18e94c204e3968b53f83c01f1b7

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