hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10525) Allow the client to use a different thread for writing to ease interrupt
Date Mon, 24 Feb 2014 09:14:29 GMT

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

Nicolas Liochon commented on HBASE-10525:

bq. when the connection.interrupt() is invoked the reader thread gets it.. What happens to
the writer thread if it was waiting in the callsToWrite.take() call.
In #markClosed, we put a Call to the queue (the DEATH_PILL), this way the writers exits the
'take' method. The reader thread calls #markClosed on any exception, interruptions included.

> Allow the client to use a different thread for writing to ease interrupt
> ------------------------------------------------------------------------
>                 Key: HBASE-10525
>                 URL: https://issues.apache.org/jira/browse/HBASE-10525
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.99.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.99.0
>         Attachments: 10525.v1.patch, 10525.v2.patch, 10525.v3.patch, 10525.v4.patch,
10525.v5.patch, 10525.v6.patch, 10525.v7.patch, HBaseclient-EventualConsistency.pdf
> This is an issue in the HBASE-10070 context, but as well more generally if you want to
interrupt an operation with a limited cost. 
> I will attach a doc with a more detailed explanation.
> This adds a thread per region server; so it's otional. The first patch activates it by
default to see how it behaves on a full hadoop-qa run. The target is to be unset by default.

This message was sent by Atlassian JIRA

View raw message