[
https://issues.apache.org/jira/browse/CASSANDRA-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Folke Behrens updated CASSANDRA-1355:
-------------------------------------
Attachment: 0002-conditional-wrapping.patch.txt
That's the point. Don't do it client-side. Don't trust the client, the network
and the RPC service. E.g., for CASSANDRA-1235 I had to add and alter logging
messages to find the culprit.
Patch 0002 adds a static wrap() method that wraps CassandraServer only if debug
logging is enabled at start-up. Now it's useful in a non-intrusive way.
> Log RPC exceptions and timing data
> ----------------------------------
>
> Key: CASSANDRA-1355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1355
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Folke Behrens
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 0001-RPCLogger.patch, 0002-conditional-wrapping.patch.txt
>
>
> Attached patch introduces a logger that sits between Cassandra.Processor and
> CassandraServer. It logs exceptions before they get send to the client and it
> can output timing and tracing information. Pretty useful.
> This extra layer would actually be a good place for authentication and
> authorization as well.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
