Match manager tasks' timeout with the data size of the cluster

scylladb / scylla-cluster-tests

Tests for Scylla Clusters

GNU Affero General Public License v3.0

55 stars 93 forks source link

Match manager tasks' timeout with the data size of the cluster #3128

Open ShlomiBalalis opened 3 years ago

ShlomiBalalis commented 3 years ago

At the moment, when a manager repair or backup nemesis runs on any sct longevity, the time before sct forcefully stop the task and declare a timeout and a nemesis failure is set in stone no matter the scenario. i.e. whether the nemesis runs on a 10gb cluster or a 1TB cluster it will wait the same amount of time.

We should make the timeout more flexible, and dependent on the size of the scenario

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 2 years with no activity. Remove stale label or comment or this will be closed in 2 days.

fruch commented 1 year ago

Adaptive timeout could cover this case