cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3661) Re-introduce timeout debug messages in CassandraServer
Date Thu, 22 Dec 2011 17:39:33 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174921#comment-13174921
] 

Jonathan Ellis commented on CASSANDRA-3661:
-------------------------------------------

+1
                
> 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

        

Mime
View raw message