[
https://issues.apache.org/jira/browse/HBASE-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113905#comment-13113905
]
Hudson commented on HBASE-4280:
-------------------------------
Integrated in HBase-TRUNK #2247 (See
[https://builds.apache.org/job/HBase-TRUNK/2247/])
HBASE-4280 [replication] ReplicationSink can deadlock itself via handlers
jdcryans :
Files :
* /hbase/trunk/CHANGES.txt
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
> [replication] ReplicationSink can deadlock itself via handlers
> --------------------------------------------------------------
>
> Key: HBASE-4280
> URL: https://issues.apache.org/jira/browse/HBASE-4280
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.4
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.90.5
>
> Attachments: HBASE-4280-0.90.patch
>
>
> I've experienced this problem a few times, ReplicationSink calls are received
> through the normal handlers and potentially can call itself which, in certain
> situations, call fill up all the handlers. For example, 10 handlers that are
> all replication calls are all trying to talk to the local server at the same
> time.
> HRS.replicateLogEntries should have @QosPriority(priority=HIGH_QOS) to use
> the other set of handlers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
