[SERVER-30667] Recover to a Timestamp Up/Down Testing: Successful Upgrade/Downgrade Scenario Created: 15/Aug/17 Updated: 06/Dec/22 Resolved: 06/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cristopher Stauffer | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | rollback-optional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Scenarios: As an administrator with a 3.4 mongod instance,
As an administrator with a 3.6 mongod instance and FCV 3.4,
|
| Comments |
| Comment by Cristopher Stauffer [ 29/Aug/17 ] |
|
I agree about your comment on standalone. I'll update it. This is intended as a future test for the multi-version test suite. |
| Comment by Susan LoVerso [ 29/Aug/17 ] |
|
cristopher.stauffer I'm not sure if this is a future unit test outline or something else. Let me elaborate on what you've written for clarification. First I suggest the term standalone instead of single instance because that phrase can be confused with single node replica set. When running a 3.6 binary (regardless of FCV value):
If you perform a clean shutdown of a 3.6 binary and FCV 3.4 and restart with a 3.4 binary your statements are correct that all collection statuses should yield log=true. |