You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2018/12/11 22:33:00 UTC

[jira] [Updated] (HBASE-17959) Canary timeout should be configurable on a per-table basis

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

Andrew Purtell updated HBASE-17959:
-----------------------------------
    Fix Version/s: 1.3.3

> 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
>             Fix For: 1.4.0, 1.3.3, 2.0.0
>
>         Attachments: HBASE-17959-branch-1.patch, HBASE-17959.002.patch, HBASE-17959.003.patch, HBASE-17959.004.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
(v7.6.3#76005)