Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible

ContinuousAddRemoveShard uses the FlagBasedThreadLifecycle type which means that it doesn't take special care to synchronize with the $config.setup() and $config.teardown() functions in FSM workloads: even during these methods it will continue to run.

By having the ContinuousAddRemoveShard hook be able to use either FlagBasedThreadLifecycle or FileBasedThreadLifeCycle, which synchronizes with the FSM framework (example of ContinuousStepdown which does this), the ContinuousAddRemoveShard hook will no longer run while setup() and teardown() are ongoing.

depends on

SERVER-95424 Allow hooks that use the FileBasedThreadLifecycle to be stackable

Closed

is depended on by

SERVER-95333 Mark only FSM workloads that use a getMore outside of setup() / teardown() with "requires_getmore"

Closed

is related to

SERVER-90465 Evaluate and add additional coverage for untracked unsharded collections

Closed

SERVER-90706 Add requires_getmore tag to concurrency and jscore tests that run getMore but do not currently have this tag

Closed

related to

SERVER-95379 Get rid of TestData.useActionPermittedFile

Needs Scheduling

SERVER-95380 Abstract away ThreadLifecycle object and get rid of the is_fsm_workload / use_action_permitted_file variable

Needs Scheduling

(1 related to)

Assignee:: Vishnu Kaushik

Reporter:: Vishnu Kaushik

Participants:: Githook User, Vishnu Kaushik

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: Sep 25 2024 09:10:31 PM UTC

Updated:: Oct 03 2024 06:53:10 PM UTC

Resolved:: Oct 03 2024 06:53:09 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates