hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
Date Fri, 13 Mar 2015 17:25:39 GMT

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

Nick Dimiduk commented on HBASE-13219:

Yikes! Yes, I would think --oneCon should be the culprit. Why do we have the option for multiple
connections at all? In mapped mode, each mapper will do it's thing. In --nomapred, it's multiple
threads, should all share the single connection.

Best to remove --oneCon entirely and have that be the default mode. Do I have that wrong?

> 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: t1
> -> PE tool tries to create the TEstTable and waits for it to be enabled and just hangs
> 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

View raw message