Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make c-s to print stacktrace of all threads when it is getting forcefully killed, say getting SIGKILL and SIGABRT. #28

Open
dkropachev opened this issue Oct 20, 2024 · 5 comments
Assignees

Comments

@dkropachev
Copy link
Contributor

dkropachev commented Oct 20, 2024

We have couple of cases when c-s stucks not generating any traffic and even not terminating in time.
To investigate it furthere we need to have ability to see what threads are doing.

@kbr-scylla
Copy link

Yes please!
we have multiple tests where c-s is hanging
here's another one: scylladb/scylladb#16219

@kbr-scylla
Copy link

Another: scylladb/scylladb#15918

@Bouncheck
Copy link
Contributor

I've created a PR, but I cannot add reviewers there. @dkropachev please check if it solves this issue.
Unfortunately I think there's nothing on application level that we can do about SIGKILL.

@dkropachev
Copy link
Contributor Author

I've created a PR, but I cannot add reviewers there. @dkropachev please check if it solves this issue.

Done

Unfortunately I think there's nothing on application level that we can do about SIGKILL.

Not a problem any signal would be enough.

@roydahan
Copy link
Contributor

This should be opened in the correct repository for cassandra-stress --> https://github.com/scylladb/cassandra-stress.
Moving.

@roydahan roydahan transferred this issue from scylladb/scylla-tools-java Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants