You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scylla version: 2025.1.0~rc2-20250216.6ee17795783f with build-id 8fc682bcfdf0a8cd9bc106a5ecaa68dce1c63ef6
Kernel Version: 6.8.0-1021-aws
Issue description
This issue is a regression.
It is unknown if this issue is a regression.
Looks like this test is too heavy for db cluster - especially on disk. I tried it with i4i.4xlarge and still having very high cluster usage (in regards to CPU it was very similar to i3en.xlarge, but disk throughput was very high). Reposting my analysis:
User profile has set for clustering key setting cluster: uniform(1..100). This way each insert is actually 50 rows insert (in average) per operation see c-s result:
And because rows are big (5 columns, 1024 bytes each) and 2 MV and 2 indexes makes this test very difficult for disk (when c-s error happened, there was around 950MB/s of reads and 850MB/s disk write load) for given io_properties reaching read 3GB/s and write 2GB/s (which I think compete with each other, along with iops). loaders still was very quiet (~15% cpu load).
In my opinion disk is too heavy loaded, we should reduce the column sizes or row count per pk.
Impact
The test is never passing and it's hard to track regressions with it (it never passed in history due overload or enospc)
OS / Image: ami-00dd94413096f919a (aws: undefined_region)
Test: longevity-double-cluster-with-schema-changes-vnodes-test
Test id: 558d26a2-a8eb-4110-8dce-c7d95875dd8c
Test name: scylla-2025.1/vnodes/tier2/longevity-double-cluster-with-schema-changes-vnodes-test
Test method: longevity_test.LongevityTest.test_custom_time
Test config file(s):
Packages
Scylla version:
2025.1.0~rc2-20250216.6ee17795783f
with build-id8fc682bcfdf0a8cd9bc106a5ecaa68dce1c63ef6
Kernel Version:
6.8.0-1021-aws
Issue description
Looks like this test is too heavy for db cluster - especially on disk. I tried it with i4i.4xlarge and still having very high cluster usage (in regards to CPU it was very similar to i3en.xlarge, but disk throughput was very high). Reposting my analysis:
User profile has set for clustering key setting cluster: uniform(1..100). This way each insert is actually 50 rows insert (in average) per operation see c-s result:
And because rows are big (5 columns, 1024 bytes each) and 2 MV and 2 indexes makes this test very difficult for disk (when c-s error happened, there was around 950MB/s of reads and 850MB/s disk write load) for given io_properties reaching read 3GB/s and write 2GB/s (which I think compete with each other, along with iops). loaders still was very quiet (~15% cpu load).
In my opinion disk is too heavy loaded, we should reduce the column sizes or row count per pk.
Impact
The test is never passing and it's hard to track regressions with it (it never passed in history due overload or enospc)
How frequently does it reproduce?
100%
Installation details
Cluster size: 3 nodes (i4i.4xlarge)
Scylla Nodes used in this run:
OS / Image:
ami-00dd94413096f919a
(aws: undefined_region)Test:
longevity-double-cluster-with-schema-changes-vnodes-test
Test id:
558d26a2-a8eb-4110-8dce-c7d95875dd8c
Test name:
scylla-2025.1/vnodes/tier2/longevity-double-cluster-with-schema-changes-vnodes-test
Test method:
longevity_test.LongevityTest.test_custom_time
Test config file(s):
Logs and commands
$ hydra investigate show-monitor 558d26a2-a8eb-4110-8dce-c7d95875dd8c
$ hydra investigate show-logs 558d26a2-a8eb-4110-8dce-c7d95875dd8c
Logs:
Jenkins job URL
Argus
The text was updated successfully, but these errors were encountered: