Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.1, 4.2.2
Affects Version/s: None
Component/s: Replication, Sharding, Testing Infrastructure
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.2
Sprint:
Repl 2019-05-20, Repl 2019-06-03, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09, Repl 2019-09-23
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

We have kill and terminate versions of jscore passthroughs but not the step down suites. Since we do already have the step down concurrency suites, this shouldn't be too much work but would add good failover/concurrency coverage.

depends on

SERVER-39770 FSM connection cache setup can fail with step down

Closed

SERVER-41096 ContinuousStepdown thread and resmoke runner do not synchronize properly on the "stepdown permitted file" and "stepping down file"

Closed

SERVER-41113 Ignore NamespaceNotFound exceptions when applying transactions during initial sync and recovery

Closed

is depended on by

SERVER-39994 Add concurrency_simultaneous_sharding_with_stepdowns|terminates|kills.yml

Blocked

is related to

SERVER-39992 Add failovers to concurrency_sharded_replication_multi_stmt_txn.yml

Closed

related to

SERVER-39995 Add concurrency_simultaneous_sharding.yml

Backlog

(1 related to)

Assignee:: Vesselina Ratcheva (Inactive)
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer, Vesselina Ratcheva
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 06 2019 07:43:47 PM UTC
Updated:: Oct 29 2023 10:23:14 PM UTC
Resolved:: Sep 11 2019 07:12:36 PM UTC
Confidence Status Last Update:: 09/Jul/19 9:36 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates