hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4280) [replication] ReplicationSink can deadlock itself via handlers
Date Wed, 16 Nov 2011 19:43:52 GMT

     [ https://issues.apache.org/jira/browse/HBASE-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hsieh updated HBASE-4280:
----------------------------------

    Fix Version/s: 0.94.0
                   0.92.0
    
> [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.92.0, 0.94.0, 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.
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

        

Mime
View raw message