[SERVER-25787] ReplSetTest.awaitReplication() should compare terms Created: 25/Aug/16 Updated: 31/Oct/16 Resolved: 27/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | William Schultz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
ReplSetTest.awaitReplicaiton() only checks timestamp, so it doesn't catch the oplog divergence if the old and new primary write oplog during the same second. |
| Comments |
| Comment by Githook User [ 27/Oct/16 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: |
| Comment by Judah Schvimer [ 07/Sep/16 ] |
|
We already have functions _getLastOpTime() and _isEarlierOpTime() which can be used to get and compare optimes properly. |