[SERVER-47489] replica_set_multiversion tests can depend on standalones illegally downgrading Created: 11/Apr/20  Updated: 29/Oct/23  Resolved: 17/Apr/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc2, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Repl 2020-04-20
Participants:
Linked BF Score: 46

 Description   

replica_set_multiversion will randomly choose between "latest" and "last-stable" when starting up a mongod instance. The passthrough logic is smart enough to downgrade the FCV and clean shutdown, but that's not sufficient for ensuring "last-stable" is always able to start up in more complicated restart sequences. Consider the following (using 4.4/4.2 as an example):

  1. Start MongoDB 4.4 + ReplSet
  2. SetFCV 4.2
  3. Shutdown (MongoDB 4.2 can restart on these data files)
  4. Start MongoDB 4.4 + Standalone
  5. Shutdown (MongoDB 4.2 can not restart on these data files)


 Comments   
Comment by Githook User [ 21/Apr/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-47489 Blacklist standalone_replication_recovery_idempotent.js and temp_namespace_restart_as_standalone from multiversion testing

(cherry picked from commit 3c3661f83ab419b533b7ed8cfaede2fc8ba7a780)
Branch: v4.4
https://github.com/mongodb/mongo/commit/b38c6815cee932098722b72430b3237da3fe312a

Comment by Githook User [ 17/Apr/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-47489 Blacklist standalone_replication_recovery_idempotent.js and temp_namespace_restart_as_standalone from multiversion testing
Branch: master
https://github.com/mongodb/mongo/commit/3c3661f83ab419b533b7ed8cfaede2fc8ba7a780

Comment by Jason Chan [ 17/Apr/20 ]

This ticket will blacklist both standalone_replication_recovery_idempotent.js and temp_namespace_restart_as_standalone from multiversion testing.

Comment by Judah Schvimer [ 13/Apr/20 ]

I support just blacklisting the test to avoid a bunch of extra complexity.

Comment by Daniel Gottlieb (Inactive) [ 11/Apr/20 ]

Or just omit standalone_replication_recovery_idempotent.js from being run

Generated at Thu Feb 08 05:14:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.