[
https://issues.apache.org/jira/browse/HBASE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449409#comment-13449409
]
stack commented on HBASE-6165:
------------------------------
@Jeff IIRC they need to be on a channel other than user priority queue because
they can overwhelm user loadings (e.g. big cluster replication into small
cluster). We've been learning a bunch of late about replicating and its fair
to say that some pieces need a bit of rethink making them more robust around
cases such as aforementioned large into small or one we ran into ourselves
recently where we couldn't start the small cluster because the high priority
handlers were all occupied by replication soon after startup (This patch would
help w/ that scenario). I see that this patch has just been backported to 0.92
-- hopefully that will be of help to you in your current predicament.
> Replication can overrun .META. scans on cluster re-start
> --------------------------------------------------------
>
> Key: HBASE-6165
> URL: https://issues.apache.org/jira/browse/HBASE-6165
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Himanshu Vashishtha
> Fix For: 0.96.0, 0.94.2
>
> Attachments: 6165-v6.txt, HBase-6165-94-v1.patch,
> HBase-6165-94-v2.patch, HBase-6165-v1.patch, HBase-6165-v2.patch,
> HBase-6165-v3.patch, HBase-6165-v4.patch, HBase-6165-v5.patch
>
>
> When restarting a large set of regions on a reasonably small cluster the
> replication from another cluster tied up every xceiver meaning nothing could
> be onlined.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
