hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kulkarni (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17959) Canary timeout should be configurable on a per-table basis
Date Mon, 22 May 2017 22:20:05 GMT

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

Chinmay Kulkarni updated HBASE-17959:
    Attachment: HBASE-17959.003.patch

[~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.

> 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

View raw message