[SERVER-45311] Fix retryable_write_concern.js in replica_sets_multiversion suite Created: 27/Dec/19 Updated: 29/Oct/23 Resolved: 03/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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 | ||||
| Sprint: | Repl 2020-01-13 | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
I am not sure what was the special case we wanted to test to set FCV in the middle of the test (added in |
| Comments |
| Comment by Githook User [ 03/Jan/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |
| Comment by Lingzhi Deng [ 02/Jan/20 ] |
|
Agreed. Splitting the test makes sense. Thanks. |
| Comment by Judah Schvimer [ 02/Jan/20 ] |
|
lingzhi.deng, the test sets the FCV as a way of testing that the setFeatureCompatibilityVersion command waits for write concern on retries. I added that to give the test greater breadth and test that specific behavior which I noticed was missing from the test. I think we should split testing that command into its own test that is multiversion incompatible so we can keep the rest of the test in multiversion suites. |