[SERVER-33525] Fix replication and sharding tests to work with RTT Created: 27/Feb/18  Updated: 27/Oct/23  Resolved: 23/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Gone away Votes: 0
Labels: rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32144 Remove test coverage for replication ... Closed
depends on SERVER-33165 Don't return from ReplSetTest.initiat... Closed
depends on SERVER-34070 Add flag to perform replication recov... Closed
Related
is related to SERVER-34126 config_version_rollback.js runs with ... Closed
is related to SERVER-29051 RollbackImpl should create rollback d... Closed
is related to SERVER-31239 Disable resync command and remove tests Closed
is related to SERVER-33488 WT SizeStorer dislikes RTT Closed
is related to SERVER-33590 Add targeted rollback test for rollba... Closed
is related to SERVER-34099 Clear config version cache on rollbac... Closed
Sprint: Repl 2018-03-12, Repl 2018-03-26, Repl 2018-04-09, Repl 2018-04-23, Repl 2018-05-07
Participants:

 Comments   
Comment by Judah Schvimer [ 23/Apr/18 ]

Closing this ticket since all tests have been turned into unittests, fixed, marked as irrelevant, or had separate tickets filed for them.

Comment by Judah Schvimer [ 29/Mar/18 ]

Remaining work on this ticket is to fix
temp_namespace_restart_as_standalone.js: Ensure that the collection creation is in the stable checkpoint before shutting down the node. SERVER-33165
clean_shutdown_oplog_state.js: If we restart at a stable checkpoint, change the test success criteria. SERVER-33165

Comment by Judah Schvimer [ 08/Mar/18 ]

resync.js: Add "requires_mmapv1" until the test is removed in SERVER-31239

Comment by Judah Schvimer [ 02/Mar/18 ]

apply_batch_only_goes_forward.js succeeds because we clear the appliedThrough on clean shutdown.

Comment by Daniel Gottlieb (Inactive) [ 02/Mar/18 ]

The following tests, unintentionally provide coverage that count is correct across restarts. They will temporarily be changed to use find().itcount() and change back to "fast-count" after SERVER-33488

 jstests/auth/upgrade_noauth_to_keyfile.js                |  6 +++---
 jstests/ssl/upgrade_noauth_to_x509_ssl.js                |  6 +++---
 jstests/ssl/upgrade_to_ssl.js                            |  8 ++++----
 jstests/ssl/upgrade_to_x509_ssl.js                       |  8 ++++----
 jstests/sslSpecial/upgrade_noauth_to_x509_nossl.js       |  4 ++--
 jstests/sslSpecial/upgrade_to_ssl_nossl.js               |  6 +++---
 jstests/sslSpecial/upgrade_to_x509_ssl_nossl.js          | 10 +++++-----

Comment by Judah Schvimer [ 01/Mar/18 ]

apply_batch_only_goes_forward.js is succeeding, but it manually modifies minValid so I don't know why.

Comment by Judah Schvimer [ 27/Feb/18 ]

The broken sharding tests are:
config_version_rollback.js: Add "requires_mmapv1" tag and convert to an OpObserver unittest.
shard_aware_init.js: Fix the test by turning off --replSet

The broken replication tests are:
double_rollback.js: Add "requires_mmapv1" since rollback no longer has a minValid post rollback and should be able to sync from any node.
double_rollback_early.js: Add "requires_mmapv1" since rollback no longer has a minValid post rollback and should be able to sync from any node, and add a new test that rollback can sync from its sync source again after rollback, and after its sync source rolled back behind the common point. The roll back node should then roll back again to an even farther back point. (SERVER-33590)
rollback_cmd_unrollbackable.js: Add "requires_mmapv1" since all commands are rollbackable now.
rollback_collMod_fatal.js: Add "requires_mmapv1" since collmods are no longer fatal
rollback_creates_rollback_directory.js: Add "requires_mmapv1" until SERVER-29051 is complete.
oplog_replay_on_startup.js: Replace coverage with unittest coverage in SERVER-33292
oplog_truncate_on_recovery.js: Replace coverage with unittest coverage in SERVER-33292
oplog_replay_on_startup_update_and_delete.js: Replace coverage with unittest coverage in SERVER-33292
oplog_replay_on_startup_with_bad_op.js: Replace coverage with unittest coverage in SERVER-33292. This test doesn't fail right now because it expects an fassert, but is getting the wrong fassert.
temp_namespace_restart_as_standalone.js: Ensure that the collection creation is in the stable checkpoint before shutting down the node. SERVER-33165
clean_shutdown_oplog_state.js: If we restart at a stable checkpoint, change the test success criteria. SERVER-33165

replica_sets_pv0 tests will be deleted with SERVER-32144.

Generated at Thu Feb 08 04:33:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.