[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: |
|
||||||||||||||||
| 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: Revert changes to onMigrateCompletedOnPrimary to make it easier for secondary to replicate config.transactions idempotently. (cherry picked from commit 57d007e00124d18e94c204e3968b53f83c01f1b7) |
| Comment by Githook User [ 27/Sep/18 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}Message: Revert changes to onMigrateCompletedOnPrimary to make it easier for secondary to replicate config.transactions idempotently. (cherry picked from commit 57d007e00124d18e94c204e3968b53f83c01f1b7) |
| Comment by Githook User [ 27/Aug/18 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}Message: Revert changes to onMigrateCompletedOnPrimary to make it easier for secondary to replicate config.transactions idempotently. |