[SERVER-42024] shards_and_config_return_last_committed_optime.js shouldn't assume opTime in response equals opTime in metadata Created: 01/Jul/19 Updated: 29/Oct/23 Resolved: 02/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.11, 4.2.0-rc3, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| 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.2, v4.0
|
||||||||
| Sprint: | Sharding 2019-07-15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 12 | ||||||||
| Description |
|
shards_and_config_return_last_committed_optime.js runs replSetGetStatus and asserts the last committed opTime timestamp in the response's body equals the last committed opTime metadata field in the response, which may not be true if the last committed opTime advances between executing the command and computing its metadata. The test should assert the last committed opTime in the metadata is >= the opTime in the response body instead. |
| Comments |
| Comment by Githook User [ 11/Jul/19 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: (cherry picked from commit 47c4ce9e44df98b6b5c2586c73f6b25e29722414) |
| Comment by Githook User [ 11/Jul/19 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 47c4ce9e44df98b6b5c2586c73f6b25e29722414) |
| Comment by Githook User [ 02/Jul/19 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |