Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2FB4E174C1 for ; Thu, 12 Mar 2015 12:39:39 +0000 (UTC) Received: (qmail 18250 invoked by uid 500); 12 Mar 2015 12:39:38 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 18081 invoked by uid 500); 12 Mar 2015 12:39:38 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 17847 invoked by uid 99); 12 Mar 2015 12:39:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2015 12:39:38 +0000 Date: Thu, 12 Mar 2015 12:39:38 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (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 ramkrishna.s.vasudevan created HBASE-13219: ---------------------------------------------- Summary: 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 -> 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 task, int callTimeout, int id) { QueueingFuture newFuture = new QueueingFuture(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)