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
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