[SERVER-42453] ensure current clusterTime is greater than afterClusterTime value for read in step_down_on_secondary.js Created: 26/Jul/19 Updated: 29/Oct/23 Resolved: 29/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 9 | ||||||||
| Description |
|
In step_down_on_secondary.js, if we attempt to perform an afterClusterTime read at the timestamp greater than the current clusterTime, we will receive an error. We should make sure the clusterTime is advanced before performing this read. |
| Comments |
| Comment by Githook User [ 15/Aug/19 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}Message: (cherry picked from commit 4ae9ca6543819f7b6915b18ebf30e7633da78442) |
| Comment by Githook User [ 26/Jul/19 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'username': 'pvselvan', 'email': 'pvselvan@umich.edu'}Message: |