hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4280) [replication] ReplicationSink can deadlock itself via handlers
Date Wed, 14 Sep 2011 18:30:09 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104753#comment-13104753

Jean-Daniel Cryans commented on HBASE-4280:

It seems like we shouldn't be the ones deciding that... but currently the user has no control
over QOS since it's hard-coded.

> [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


View raw message