You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/04/21 23:27:05 UTC
[jira] [Created] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Log read timeouts at the StorageProxy level
-------------------------------------------
Key: CASSANDRA-2532
URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
Project: Cassandra
Issue Type: Bug
Reporter: Stu Hood
Fix For: 0.8.0
We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-2532:
--------------------------------
Attachment: 0002-Remove-useless-timeout-entries-in-thrift.CS.txt
0002 removes the useless timeout entry from thrift.CassandraServer for symmetry.
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt, 0002-Remove-useless-timeout-entries-in-thrift.CS.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-2532:
--------------------------------
Attachment: 0001-Log-timeouts-in-SP.txt
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022970#comment-13022970 ]
Stu Hood commented on CASSANDRA-2532:
-------------------------------------
Done in 0003
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt, 0002-Remove-useless-timeout-entries-in-thrift.CS.txt, 0003-Log-write-timeouts-in-SP.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024808#comment-13024808 ]
Hudson commented on CASSANDRA-2532:
-----------------------------------
Integrated in Cassandra-0.8 #37 (See [https://builds.apache.org/hudson/job/Cassandra-0.8/37/])
centralize timeout logging in StorageProxy, and preserve the timeoutexception message
patch by Stu Hood; reviewed by jbellis for CASSANDRA-2532
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Assignee: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt, 0002-Remove-useless-timeout-entries-in-thrift.CS.txt, 0003-Log-write-timeouts-in-SP.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022935#comment-13022935 ]
Jonathan Ellis commented on CASSANDRA-2532:
-------------------------------------------
can we do inserts too for consistency?
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt, 0002-Remove-useless-timeout-entries-in-thrift.CS.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-2532:
--------------------------------
Attachment: 0003-Log-write-timeouts-in-SP.txt
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt, 0002-Remove-useless-timeout-entries-in-thrift.CS.txt, 0003-Log-write-timeouts-in-SP.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2532) Log read timeouts at the
StorageProxy level
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022928#comment-13022928 ]
Jonathan Ellis commented on CASSANDRA-2532:
-------------------------------------------
as discussed on irc, we should centralize timeout logging in SP rather than mixing it into both CassandraServer + SP.
> Log read timeouts at the StorageProxy level
> -------------------------------------------
>
> Key: CASSANDRA-2532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2532
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stu Hood
> Fix For: 0.8.0
>
> Attachments: 0001-Log-timeouts-in-SP.txt
>
>
> We log successful reads, but not timeouts (although we have a lovely TimeoutException message, it doesn't look like we are printing it).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira