-
Notifications
You must be signed in to change notification settings - Fork 82
/
longevity-5000-tables.yaml
39 lines (27 loc) · 1.04 KB
/
longevity-5000-tables.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
test_duration: 2160
cs_duration: '55m'
cs_user_profiles:
- scylla-qa-internal/cust_d/templated_tables_mv.yaml
pre_create_schema: true
user_profile_table_count: 5000
batch_size: 100
n_loaders: 5
n_monitor_nodes: 1
n_db_nodes: 1
add_node_cnt: 5
jmx_heap_memory: 1024 # this is a fix/workaround for https://github.com/scylladb/scylla/issues/7609
instance_type_db: 'i3.8xlarge'
instance_type_loader: 'c5.4xlarge'
user_prefix: 'longevity-5000-tables'
root_disk_size_runner: 120
cluster_health_check: false
nemesis_class_name: 'SisyphusMonkey'
nemesis_seed: '404'
nemesis_interval: 60
# TODO: enable back coredump on bad_alloc
# scylla/issues/4764 was blocking progress into the production issues we were trying to reproduce
# so we temporary removed the default `--abort-on-lsa-bad-alloc 1 --abort-on-seastar-bad-alloc`
# once the issue would be solved we can enable it back.
append_scylla_args: '--blocked-reactor-notify-ms 500'
# TODO: remove when https://github.com/scylladb/scylla-tools-java/issues/175 resolved
stop_test_on_stress_failure: false