hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17296) Provide per peer throttling for replication
Date Wed, 14 Dec 2016 08:53:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747717#comment-15747717

Guanghao Zhang commented on HBASE-17296:

Found a bug in ReplicationPeersZKImpl.updatePeerConfig. It didn't update table cfs config
and no ut check this... I fix it in this branch-1 patch. But the proper way is open a issue
to fix this bug? [~tedyu@apache.org]

> 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
>            Assignee: Guanghao Zhang
>         Attachments: HBASE-17296-branch-1.patch, HBASE-17296-branch-1.patch, 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

View raw message