[SERVER-68146] Test running all commands in the downgrading state and after transitioning back to upgraded Created: 19/Jul/22 Updated: 29/Oct/23 Resolved: 22/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Huayu Ouyang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-2821-milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2022-08-22, Repl 2022-09-05, Repl 2022-09-19, Repl 2022-10-03 | ||||||||
| Participants: | |||||||||
| Description |
|
Create a basic test similar to read_write_concern_defaults_application.js/db_reads_while_recovering_all_commands.js to go through all the possible commands and make sure that if a node fails downgrade, the command can run successfully in downgrading, and then when we go back up to upgraded, the command can also run successfully there. We should test on a standalone node, a replica set, and a sharded cluster If a command needs to be skipped because it is a new feature, it can be added to a skip list. |
| Comments |
| Comment by Githook User [ 21/Sep/22 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |