cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10241) Keep a separate production debug log for troubleshooting
Date Thu, 10 Sep 2015 17:08:45 GMT


Jonathan Ellis commented on CASSANDRA-10241:

I'd like to emphasize that we're not talking about turning debug or trace on for client-generated
request paths.  There's way too much data generated and it's unlikely to be useful.

What we're proposing is enabling debug logging ONLY for cluster state changes like gossip
and schema, and infrequent activities like repair.  These are categories that we've historically
had trouble tracking down bugs in, so if we give operators on-by-default debug logging there,
the chances that they have something useful to attach to a bug report goes up immensely.

> Keep a separate production debug log for troubleshooting
> --------------------------------------------------------
>                 Key: CASSANDRA-10241
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Config
>            Reporter: Jonathan Ellis
>            Assignee: Paulo Motta
>             Fix For: 2.1.x, 2.2.x, 3.0.x
> [~aweisberg] had the suggestion to keep a separate debug log for aid in troubleshooting,
not intended for regular human consumption but where we can log things that might help if
something goes wrong.

This message was sent by Atlassian JIRA

View raw message