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] [Updated] (HBASE-10525) Allow the client to use a different thread for writing to ease interrupt
Date Mon, 24 Feb 2014 10:15:21 GMT

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

Nicolas Liochon updated HBASE-10525:

      Resolution: Fixed
    Release Note: If hbase.ipc.client.allowsInterrupt is set to true (default being false),
the writes are performed in a different thread. This workarounds a Java limitation with interruptions
and i/o; and limits the impact of interrupting a client call. It's strongly recommended to
activate this parameter when using tables with multiple replicas.
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Committed to trunk, thanks for the reviews, all. (Devaraj, I understood your comment as 'ok
if', I can obviously revert / amend if you want more time for the review.). Same goes for
everyone who wants to chime in: this code is obviously critical & complex.

> 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