You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2016/12/13 05:52:58 UTC

[jira] [Updated] (HBASE-17296) Provide per peer throttling for replication

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

Guanghao Zhang updated HBASE-17296:
-----------------------------------
    Attachment: HBASE-17296.patch

> Provide per peer throttling for replication
> -------------------------------------------
>
>                 Key: HBASE-17296
>                 URL: https://issues.apache.org/jira/browse/HBASE-17296
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Guanghao Zhang
>         Attachments: HBASE-17296.patch
>
>
> HBASE-9501 added a config to provide throttling for replication. And each peer has same bandwidth up limit. In our use case, one cluster may have several peers and several slave clusters. Each slave cluster may have different scales and need different bandwidth up limit for each peer. So We add bandwidth to replication peer config and provide a shell cmd set_peer bandwidth to update the bandwidth in need. It has been used for a long time on our clusters.  Any suggestions are welcomed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)