[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362967#comment-14362967
]
ramkrishna.s.vasudevan commented on HBASE-13219:
------------------------------------------------
Here since oneCon is by default 'false' we are going with multiple connections
per thread right? (under one client). By making oneCon as true we would start
sharing the connection.
So when we don't set oneCon as true then we are behaving as it was prior to
HBASE-11390. Still we get the above mentioned exception? I tried with oneCon
as true and there is no such exception.
> 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)
