[
https://issues.apache.org/jira/browse/HBASE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432014#comment-13432014
]
Elliott Clark commented on HBASE-6165:
--------------------------------------
A better name is probably needed for the Queue. Custom doesn't really get
across what's can go into that qos level (replication).
Since this starts 0 "custom" priority handlers by default it will add another
undocumented step when enabling replication. We should either make the number
of handlers start by default > 0, or have the number depend on if replication
is enabled.
Why choose the number 5 for the priority ? Since the QOS_THRESHOLD is 10.
(Even if they are arbitrary seems like we should have some reason and a comment
about the numbering scheme.)
Thanks for doing this.
> 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
> Attachments: HBase-6165-v1.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
