hbase-issues mailing list archives

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

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

Enis Soztutar commented on HBASE-10525:

This change might have some consequences, because the connection threads will be kept for
much longer. Can we instead do this change only on the test? 
-        conf.getInt("hbase.ipc.client.connection.minIdleTimeBeforeClose", 120000); // 2 minutes
+        conf.getInt("hbase.ipc.client.connection.minIdleTimeBeforeClose", 1200000); // 20

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