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/28 09:54:03 UTC

[jira] [Resolved] (CASSANDRA-1818) Record Client API Timeouts

     [ https://issues.apache.org/jira/browse/CASSANDRA-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stu Hood resolved CASSANDRA-1818.
---------------------------------

    Resolution: Duplicate
      Assignee: Stu Hood

I guess I opened a second ticket about this: CASSANDRA-2532. Oops.

> Record Client API Timeouts
> --------------------------
>
>                 Key: CASSANDRA-1818
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1818
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>            Priority: Minor
>
> ...in the (DEBUG) logs, and as a metric. If the timed-out-request was logged in its entirety, perhaps with the remote nodes that we might have had to block for.
> (on a related topic, we don't record the full time taken for API requests: only for the storage level)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira