[
https://issues.apache.org/jira/browse/HBASE-17959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020296#comment-16020296
]
Chinmay Kulkarni edited comment on HBASE-17959 at 5/22/17 10:19 PM:
--------------------------------------------------------------------
[~apurtell] I thought this would not be necessary since we have only one
write-table, but I agree it would make logging more convenient and easier to
parse. I have split the read and write latency counters to reflect this change.
Please take a look at the amended patch.
Thanks!
was (Author: ckulkarni):
[~apurtell] I thought this would not be necessary since we have only one
write-table, but I agree it would make logging more convenient and easier to
parse. I have split the read and write latency counters to reflect this change.
Please take a look at this amended patch.
Thanks!
> 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.003.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)
