[
https://issues.apache.org/jira/browse/HBASE-17959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018066#comment-16018066
]
Andrew Purtell commented on HBASE-17959:
----------------------------------------
{code}
+ LOG.info("Read/Write operation for " + tableName + " took " +
actual +
+ " ms. The configured timeout was " + configured + " ms.");
{code}
So the question I would ask when seeing this log line as an operator, is was it
a read or write operation that timed out.
> Canary timeout should be configurable on a per-table basis
> ----------------------------------------------------------
>
> Key: HBASE-17959
> URL: https://issues.apache.org/jira/browse/HBASE-17959
> Project: HBase
> Issue Type: Improvement
> Components: canary
> Reporter: Andrew Purtell
> Assignee: Chinmay Kulkarni
> Priority: Minor
> Attachments: HBASE-17959.002.patch, HBASE-17959.patch
>
>
> The Canary read and write timeouts should be configurable on a per-table
> basis, for cases where different tables have different latency SLAs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
