Israel Fruchter

> I could not produce with scylla-bench > ``` > start n1,n2,n3 > run scylla-bench > upgrade n3 > run scylla-bench in the background > run repair scylla-bench on n3...

More times it happened: ## Installation details Kernel Version: 5.13.0-1021-aws Scylla version (or git commit hash): `5.0~rc3-20220406.f92622e0d` with build-id `2b79c4744216b294fdbd2f277940044c899156ea` Cluster size: 6 nodes (i3.large) OS / Image: `ami-0e4ae5e4a139c50f3` (aws:...

@slivne @eliransin Happens also on 4.6.3, so it's no regression: Kernel Version: 5.11.0-1022-aws Scylla version (or git commit hash): `4.6.3-20220414.8bf149fdd` with build-id `8d16d8972498cc769071ff25309b009eb77bf77a` Cluster size: 6 nodes (i3.large) OS /...

> @roydahan does it happen all the time. > Can I have a reproducer job so I can debug? you can use https://jenkins.scylladb.com/view/master/job/scylla-master/job/reproducers/job/longevity-harry-2h-test/, it a 2.5h run. > Did we...

> Where is the cassandra-harry log (on which tar file?) in the loader-set

> Looks like https://python-driver.docs.scylladb.com is down! > It's now back I had to rerun https://github.com/scylladb/python-driver/actions/runs/3081512538/jobs/5010170489 Seems like it's my mistake that I didn't push the changes to the documention (pointing...

@asias would `nodetool removenode` would need similar issue ? or there we don't relay on gossip, since the node is dead already ? (i.e. trying to think if there are...

> > @asias would `nodetool removenode` would need similar issue ? or there we don't relay on gossip, since the node is dead already ? (i.e. trying to think if...

@xemul @bhalevy happened again on 5.0 next: https://jenkins.scylladb.com/job/scylla-5.0/job/next/204/artifact/logs-gating.release.2/1663603045422_update_cluster_layout_tests.py%3A%3ATestUpdateClusterLayout%3A%3Atest_simple_kill_node_while_decommissioning/

@tnozicka are the new feature flags going to be expose in the helm chart ? (i.e. in SCT we are deploying using the helm chart)