Open vponomaryov opened 1 year ago
At first, the issue was filed here: https://github.com/scylladb/scylladb/issues/14120 Moving it here for further investigation from the QA side. As a first step, triggered the ReRun to see it's repeatability.
The ReRun has successfully passed: https://jenkins.scylladb.com/job/scylla-5.2/job/longevity/job/longevity-10gb-3h-gce-test/19/console
Issue description
Impact
Describe the impact this issue causes to the user.
How frequently does it reproduce?
1/1
Installation details
Kernel Version: 5.19.0-1024-gcp Scylla version (or git commit hash):
5.2.2-20230530.9dd70a58c3f9
with build-idd3997884004abbd7d6f60bf507b63050c88c4cf3
Cluster size: 6 nodes (n1-highmem-16)
Scylla Nodes used in this run:
OS / Image:
https://www.googleapis.com/compute/v1/projects/scylla-images/global/images/929956698705654922
(gce: us-east1)Test:
longevity-10gb-3h-gce-test
Test id:e97657e6-8081-4001-a90b-347ede0f569d
Test name:scylla-5.2/longevity/longevity-10gb-3h-gce-test
Test config file(s):Details:
The problem appeared during the
multiple_hard_reboot_node
nemesis which has following steps:7
)And after the second reboot of the same node it generated core dump:
Note that there was no stress load at that time:
Monitoring:
$ hydra investigate show-monitor e97657e6-8081-4001-a90b-347ede0f569d
$ hydra investigate show-logs e97657e6-8081-4001-a90b-347ede0f569d
Logs:
Jenkins job URL Argus