[SERVER-30671] Don't expect operationTime to not change in causal_consistency_shell_support.js Created: 15/Aug/17 Updated: 30/Oct/23 Resolved: 01/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.11 |
| Fix Version/s: | 3.6.3, 3.7.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: |
v3.6
|
||||||||
| Sprint: | Sharding 2017-09-11, Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2017-12-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Internal activity in the config server can lead to writes that advance operationTime, which can cause causal_consistency_shell_support.js to fail when it asserts that read commands don't advance operationTime. This check should be removed since there is no way to either prevent or ignore these writes. This is the same base problem as |
| Comments |
| Comment by Githook User [ 16/Jan/18 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: (cherry picked from commit 1b3d16dc0ecfac35dbbf945a3a9f6a8cdd3226f7) |
| Comment by Githook User [ 01/Dec/17 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |