hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9501) Provide throttling for replication
Date Sat, 08 Feb 2014 00:12:19 GMT

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

Jean-Daniel Cryans updated HBASE-9501:
--------------------------------------

    Status: Patch Available  (was: Open)

bq. what about adding log and interrupting the current thread?

Sorry, that's what I meant.

A few cosmetic comments regarding the latest patch then we can commit:

 - ReplicationThrottler.enabled and bandwidth should be final.
 - ReplicationThrottler.throttling() doesn't throttle, it just computes a sleep time. I'd
name it getSleepTime().

If you're ok with those changes I'll just apply them on commit, no need for a new patch.

In the mean time I'm doing Submit Patch to see if everything builds correctly.

> Provide throttling for replication
> ----------------------------------
>
>                 Key: HBASE-9501
>                 URL: https://issues.apache.org/jira/browse/HBASE-9501
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Feng Honghua
>            Assignee: Feng Honghua
>         Attachments: HBASE-9501-trunk_v0.patch, HBASE-9501-trunk_v1.patch, HBASE-9501-trunk_v2.patch,
HBASE-9501-trunk_v3.patch
>
>
> When we disable a peer for a time of period, and then enable it, the ReplicationSource
in master cluster will push the accumulated hlog entries during the disabled interval to the
re-enabled peer cluster at full speed.
> If the bandwidth of the two clusters is shared by different applications, the push at
full speed for replication can use all the bandwidth and severely influence other applications.
> Though there are two config replication.source.size.capacity and replication.source.nb.capacity
to tweak the batch size each time a push delivers, but if decrease these two configs, the
number of pushes increase, and all these pushes proceed continuously without pause. And no
obvious help for the bandwidth throttling.
> From bandwidth-sharing and push-speed perspective, it's more reasonable to provide a
bandwidth up limit for each peer push channel, and within that limit, peer can choose a big
batch size for each push for bandwidth efficiency.
> Any opinion?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message