hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9843) Various fixes in client code
Date Fri, 25 Oct 2013 20:42:37 GMT

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

Elliott Clark commented on HBASE-9843:

bq.+      Runnable runnable = Trace.wrap("#" + id + ", AsyncProcess.sendMultiAction", new
Runnable() {
The description in the trace should always stay the same so that aggregation of the traces
by name is easy.  We can add the async processes id in an annotation if that is needed.

> Various fixes in client code
> ----------------------------
>                 Key: HBASE-9843
>                 URL: https://issues.apache.org/jira/browse/HBASE-9843
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.96.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.98.0, 0.96.1
>         Attachments: 9843-trunk.v2.patch
> This mainly fixes issues when we had "long" errors, for example a multi blocked when
trying to obtain a lock that was finally failing after 60s. Previously we were trying only
for 5 minutes. We now do all the tries. I've fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 20 tries
we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not in a very
good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.

This message was sent by Atlassian JIRA

View raw message