Israel Fruchter
Israel Fruchter
> > @mikliapko is this something that you could take care of? I mean validating that procedure described in [#3525 (comment)](https://github.com/scylladb/scylla-manager/issues/3525#issuecomment-1693310241) works fine with some proper test. When it's validated,...
> Where is the manager log? with the monitor logs, where it runs: https://cloudius-jenkins-test.s3.amazonaws.com/f00ac702-4e35-4909-b3bc-fe44d4b30ab8/20231224_180851/monitor-set-f00ac702.tar.gz
So seems like the nemesis in the test is bailing on the first sign of error. and it like that since ~2019 ```python # in `disrupt_mgmt_repair_cli` task_final_status = mgr_task.wait_and_get_final_status(timeout=86400) #...
@rayakurl, seems like the repair nemesis isn't waiting for retries (no that I can definitely tell if it should or should not) @roydahan, FYI, cause this kind of issue might...
> @fruch - is this a common use case - to run performance with nodes down? trying to understand how urgent the fix is the node wasn't down, just one...
> @fruch can you let us know which version of Scylla Manager (commit hash if the one from master) did you use for testing ? This recent PR #3461 is...
> @fruch I see that `uuid_sstable_identifier_enabled` is going to be introduced in scylla 5.4. Scylla manager is using 5.2.4 as the latest version we are validating scylla-manager against in the...
we already move to newer go version