Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1636927215.1253145837642.JavaMail.jira@brutus>
Date: Wed, 16 Sep 2009 17:03:57 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-1753) Deadlock in client using deprecated
 APIs in a multi-threaded application
In-Reply-To: <1268384410.1249694474857.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-1753.
--------------------------

    Resolution: Invalid

I just ran into this on the pset cluster.  100 threads are using same instance of HTable.  All are trying to do a put.  If regions moved around, all threads are blocked while the HTable figures new location.   Takes a good while for the 100 threads to get through the synchronization block.  This upload application should be making an HTable per thread or using htablepool.

Resolving as invalid.

> Deadlock in client using deprecated APIs in a multi-threaded application
> ------------------------------------------------------------------------
>
>                 Key: HBASE-1753
>                 URL: https://issues.apache.org/jira/browse/HBASE-1753
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Jim Kellerman
>             Fix For: 0.20.1
>
>         Attachments: load-8-7.out
>
>
> There is a deadlock somewhere in HTable or HConnectionManager when using the deprecated API in a multi-threaded application.
> I haven't had a chance to look at the thread dump in detail yet, but will attach it to this issue

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.