[
https://issues.apache.org/jira/browse/HBASE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433725#comment-13433725
]
Elliott Clark commented on HBASE-6165:
--------------------------------------
It's not that custom doesn't convey enough meaning (I could live with that).
Custom implies that there's been some modification from normal or stock. That
is not the case. These handlers are there for things that are built in.
Replication and security are core pieces of functionality. Naming things
custom gives the impression that they are not as supported as other operation,
which is not the case.
> 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: HBase-6165-v1.patch, HBase-6165-v2.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
