[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359073#comment-14359073
]
ramkrishna.s.vasudevan commented on HBASE-13219:
------------------------------------------------
I tried setting the CUSTOM_RPC_CLIENT_IMPL_CONF_KEY to RpcClientImpl. Still I
get the following stack trace
{code}
java.io.IOException: java.lang.RuntimeException: java.lang.OutOfMemoryError:
unable to create new native thread
at
org.apache.hadoop.hbase.PerformanceEvaluation.doLocalClients(PerformanceEvaluation.java:425)
at
org.apache.hadoop.hbase.PerformanceEvaluation.runTest(PerformanceEvaluation.java:1631)
at
org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:1988)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at
org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2009)
Caused by: java.lang.RuntimeException: java.lang.OutOfMemoryError: unable to
create new native thread
at
org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithoutRetries(RpcRetryingCallerImpl.java:194)
at
org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:306)
at
org.apache.hadoop.hbase.client.ClientScanner.next(ClientScanner.java:365)
at
org.apache.hadoop.hbase.PerformanceEvaluation$RandomScanWithRangeTest.testRow(PerformanceEvaluation.java:1223)
at
org.apache.hadoop.hbase.PerformanceEvaluation$Test.testTimed(PerformanceEvaluation.java:1074)
at
org.apache.hadoop.hbase.PerformanceEvaluation$Test.test(PerformanceEvaluation.java:1054)
at
org.apache.hadoop.hbase.PerformanceEvaluation.runOneClient(PerformanceEvaluation.java:1601)
at
org.apache.hadoop.hbase.PerformanceEvaluation$1.call(PerformanceEvaluation.java:407)
at
org.apache.hadoop.hbase.PerformanceEvaluation$1.call(PerformanceEvaluation.java:402)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at
java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360)
at
org.apache.hadoop.hbase.client.ResultBoundedCompletionService.submit(ResultBoundedCompletionService.java:142)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.addCallsForCurrentReplica(ScannerCallableWithReplicas.java:264)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:153)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:61)
at
org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithoutRetries(RpcRetryingCallerImpl.java:186)
... 12 more
{code}
> 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<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)
