[
https://issues.apache.org/jira/browse/HBASE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452491#comment-13452491
]
Jean-Daniel Cryans commented on HBASE-6165:
-------------------------------------------
[~whitingj], originally replication was using the normal handlers and was just
deadlocking the clusters in a different way. ReplicationSink uses the HBase
client which can block for ungodly amounts of time so it would fill up the
handlers and the RS would stop serving requests. HBASE-6550 changed the latter
that a bit by setting low timeouts via replication-specific client-side
configuration parameters (if it was using the normal client configurations it
would also affect all the other clients). With HBASE-6165 it's even safer since
replication is sandboxed.
> 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
