[
https://issues.apache.org/jira/browse/CASSANDRA-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175004#comment-13175004
]
Hudson commented on CASSANDRA-3661:
-----------------------------------
Integrated in Cassandra-0.8 #421 (See
[https://builds.apache.org/job/Cassandra-0.8/421/])
Re-introduce timeout debug messages in CassandraServer.
Patch by brandonwilliams, reviewed by jbellis for CASSANDRA-3661
brandonwilliams :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1222372
Files :
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/thrift/CassandraServer.java
> Re-introduce timeout debug messages in CassandraServer
> ------------------------------------------------------
>
> Key: CASSANDRA-3661
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3661
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Affects Versions: 0.8.0
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Priority: Trivial
> Labels: thrift
> Fix For: 0.8.10, 1.0.7
>
> Attachments: 3661.txt
>
>
> In 0.7 we log at debug when returning TOE back to the client:
> {code}
> . catch (TimeoutException e)
> {
> logger.debug("... timed out");
> throw new TimedOutException();
> }
> {code}
> This is primarily useful when reading through debug logs to make it obvious
> when StorageProxy gave up waiting and cleared its callbacks.
> At some point this got removed from 0.8+. (Or possibly never got correctly
> merged upwards.) Let's fix this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
