[
https://issues.apache.org/jira/browse/HBASE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432015#comment-13432015
]
Lars Hofhansl commented on HBASE-6165:
--------------------------------------
Patch looks good generally. Few comments:
# The naming is weird. These are not "Custom"QOS, but "Medium"QOS methods,
right?
# Is there a way to generalize this to sets of Handlers with different priority
(not important, though).
# By default now (if hbase.regionserver.custom.priority.handler.count is not
set), replicateWALEntry would use non-priority handlers... Which is not right,
I think. It should revert back to the current behavior in that case (which is
to do use the priorityQOS.
What I still do not understand... Does this problem always happen? Does it
happen because replicateWALEntry takes too long to finish? Does this only
happen when the slave is already degraded for other reasons? Should we also
work on replicateWALEntry failing faster in case of problems (shorter/fewer
retries, etc)?
> 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
