Return-Path: 
 <issues-return-187681-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2435517DEB
	for <apmail-hbase-issues-archive@www.apache.org>;
 Fri, 20 Mar 2015 09:25:39 +0000 (UTC)
Received: (qmail 47457 invoked by uid 500); 20 Mar 2015 09:25:39 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 47412 invoked by uid 500); 20 Mar 2015 09:25:38 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 47400 invoked by uid 99); 20 Mar 2015 09:25:38 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Mar 2015 09:25:38 +0000
Date: Fri, 20 Mar 2015 09:25:38 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12781483.1426163943000.154800.1426843538847@Atlassian.JIRA>
In-Reply-To: <JIRA.12781483.1426163943000@Atlassian.JIRA>
References: <JIRA.12781483.1426163943000@Atlassian.JIRA>
 <JIRA.12781483.1426163943300@arcas>
Subject: [jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

ramkrishna.s.vasudevan commented on HBASE-13219:
------------------------------------------------

Ya it is a 64 bit JVM.  I am using the same setup.  I have not changed the thread pool usage - but was something changed in the client side.  Even I could see that some time the TestAcidGuarentees was failing due to native memory issue.

> Issues with PE tool in trunk
> ----------------------------
>
>                 Key: HBASE-13219
>                 URL: https://issues.apache.org/jira/browse/HBASE-13219
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: 13219.txt, t1
>
>
> -> PE tool tries to create the TEstTable and waits for it to be enabled and just hangs there 
> Previously this was not happening and the PE tool used to run fine after the table creation.
> -> When we try to scan with 25 threads the PE tool fails after some time saying Unable to create native threads.
> I lost the Stack trace now. But I could get it easily.  It happens here 
> {code}
>   public void submit(RetryingCallable<V> task, int callTimeout, int id) {
>     QueueingFuture<V> newFuture = new QueueingFuture<V>(task, callTimeout);
>     executor.execute(Trace.wrap(newFuture));
>     tasks[id] = newFuture;
>   }
> {code}
> in ResultBoundedCompletionService. This is also new.  Previously it used to work with 25 threads without any issues. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)