Dmitriy Kruglov

Reproduced again in 2024.1.9 https://argus.scylladb.com/test/e3fc93ef-9efc-4ed1-85df-bf913acb2f73/runs?additionalRuns[]=4a0f40dd-b79c-4c74-b68f-355033fe31ac

@mikliapko after the fix was backported and merged to 2024.1 branch today, the original issue is not reproduced (on 2024.1.10), but this one popped out (during disrupt_mgmt_restore nemesis): ``` Command:...

@aleksbykov The issue reproduced in 2024.1.9 - https://argus.scylladb.com/test/c64d7261-b3df-451a-9d66-b8d6acb4cb35/runs?additionalRuns[]=227e1a0d-6187-46d7-9569-02e21b769fad. This fix was not backported - was it done intentionally maybe? Or we can follow up on it now?

@soyacz Find please below errors in db-nodes system.log in sct-results: ``` ❯ find ~/sct-results/latest/longevity-1gb-1h-nemesis-dmitriy-db-cluster-687b0d24/ -type f -exec grep -Eir "error|fail" {} \; -exec echo "===========" \; ts=2024-04-12T09:56:19.994Z caller=diskstats_linux.go:265 level=error collector=diskstats...

@soyacz There was no already a build in Jenkins as it was rotated, and probably because of that no build in Argus. I re-executed the Nemesis - [Jenkins build](https://jenkins.scylladb.com/job/scylla-staging/job/dimakr/job/longevity-5gb-1h-docker-test/47/) Still...

> is it fixed for jobs in jenkins? @soyacz Right, this is disabled for now in the master, until the change to enable executing docker backend in Jenkins is merged...

As a sanity check for the feature we selected the `[longevity-100gb-4h-test](https://jenkins.scylladb.com/job/scylla-enterprise/job/longevity/job/longevity-100gb-4h-test/)` case, to be executed with the following set of dict training parameters values (+ `internode_compression` enabled): ``` rpc_dict_training_min_time_seconds: 900...

Another cycle of longevity test was executed against `enterprise:latest` for the dict_training feature enabled, with the following specifics: - test duration was increased to 24h and test data set size...

Follow up on the remaining test cases that we planned to test the feature on: 1. Execute short longevities (100gb-4h) with and without dictionary training enabled. The case was repeated...

Tested the rolling upgrade after https://github.com/scylladb/scylla-enterprise/issues/4214 is fixed. The test passed in build https://jenkins.scylladb.com/job/scylla-staging/job/dimakr/job/enterprise-rolling-upgrade-test/7/. No errors are observed in logs around dict_training events. The used dict training and internode compression...