You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2018/11/30 12:10:00 UTC
[jira] [Updated] (CASSANDRA-14589)
CommitLogReplayer.handleReplayError should print stack traces
[ https://issues.apache.org/jira/browse/CASSANDRA-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedict updated CASSANDRA-14589:
---------------------------------
Summary: CommitLogReplayer.handleReplayError should print stack traces (was: CommitLogReplayer.handleReplayError swallows stack traces )
> CommitLogReplayer.handleReplayError should print stack traces
> --------------------------------------------------------------
>
> Key: CASSANDRA-14589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14589
> Project: Cassandra
> Issue Type: Bug
> Components: Observability
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 3.0.x
>
>
> handleReplayError does not accept an explicit Throwable parameter, so callers only integrate the exception’s message text into the log entry. This means a loss of debug information for operators.
> Note, this was fixed by CASSANDRA-8844 for 3.x+, only 3.0.x is affected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org