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.

Sign up for GitHub

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

Jump to bottom

Don't output the stacktrace for WARN logs on timeouts to C* nodes #2280

Closed
ashrayjain opened this issue Aug 24, 2017 · 2 comments
Closed

Don't output the stacktrace for WARN logs on timeouts to C* nodes #2280

ashrayjain opened this issue Aug 24, 2017 · 2 comments
Assignees
@gsheasby

Comments

@ashrayjain
Copy link
Contributor

Based on feedback from folks.
@clockfort
Copy link
Contributor

clockfort commented Aug 24, 2017 •
edited

If the stack traces are for a thread that actually has the honest-to-goodness operation on it (e.g. tells you that this timeout was caused by a KVS.getRanges() or inside of sweep, etc) I would consider them useful.

If the stacktraces are all just identical and only encompass the stack from a cassandra internal threadpool thread or something, then I agree that they are useless and should be removed.

@hsaraogi
Copy link
Contributor

hsaraogi commented Sep 4, 2017

@ashrayjain do you have an example stacktrace here?

@gsheasby gsheasby self-assigned this Sep 20, 2017
@gsheasby gsheasby mentioned this issue Sep 20, 2017
Closed
@gsheasby gsheasby mentioned this issue Oct 5, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gsheasby gsheasby

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@clockfort @ashrayjain @gsheasby @hsaraogi