[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383386#comment-14383386
]
ramkrishna.s.vasudevan commented on HBASE-13219:
We will commit this patch for now?
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383516#comment-14383516
]
Anoop Sam John commented on HBASE-13219:
I am +1 for this change and making multiCon as false by default.. (By default
use single connection). Ping [~nkeywal]
[~ndimiduk]
{code}
+final String oneCon = --oneCon=;
+if (cmd.startsWith(oneCon)) {
+ System.err.println(--oneCon option is deprecated, it is now the default
behavior.);
+}
+final String multiCon = --multiCon=;
+ if (cmd.startsWith(multiCon)) {
+opts.multiCon = Boolean.parseBoolean(cmd.substring(multiCon.length()));
+}
{code}
You missing a continue statement?
When user passed the deprecated --oneCon , still we have to use it with negate?
Or exit with error? Simply disregard this is correct?
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384079#comment-14384079
]
Nick Dimiduk commented on HBASE-13219:
--
bq. You missing a continue statement?
Yeah, probably. I didn't try it out, only hacked up what I thought it should be
doing. If this is making sense to you please move forward with the partial
patch.
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370951#comment-14370951
]
ramkrishna.s.vasudevan commented on HBASE-13219:
+1 on patch. But I would still like to know why the multicon false option does
not work as it was working previously.
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370975#comment-14370975
]
zhangduo commented on HBASE-13219:
--
Did you run it using a 64bit jvm [~ram_krish] ? I used to create over 20,000
threads in one process, it is fine if you have enough memory.
Or maybe we have changed the thread pool usage at client side?
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361720#comment-14361720
]
ramkrishna.s.vasudevan commented on HBASE-13219:
Just going thro the comments on the JIRA. So previously it was multiple
connections but still there was no thread getting exhausted? Is it due to the
recent connection change?
BTW would make the multiCon with default option as false. So that all threads
share the same connection.
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360726#comment-14360726
]
Nick Dimiduk commented on HBASE-13219:
--
From its description, it seems the default was a single shared connection.
If [~nkeywal] would like to keep the toggle, I suggest we call it --multiCon or
similar, false by default, so the common case is that all client threads share
a single connection.
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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360740#comment-14360740
]
Anoop Sam John commented on HBASE-13219:
Now the default is multiple connection. (oneCon = false).
I am +1 for keeping both options in place and default to all client threads
share a single connection.
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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360715#comment-14360715
]
Anoop Sam John commented on HBASE-13219:
What was the behavior before HBASE-11390? Multiple connections?
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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360723#comment-14360723
]
Nicolas Liochon commented on HBASE-13219:
-
bq. What was the behavior before HBASE-11390? Multiple connections?
Yeah, exactly. I kept it to make comparison between multiple versions possible.
It can help to find some bottlenecks (multiple connections means multiple tcp
connections, multiple pools and so on).
But simplicity is good as well, so both options are ok to me.
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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361603#comment-14361603
]
ramkrishna.s.vasudevan commented on HBASE-13219:
Ya sure. I Wil check this out. Excuse typos.
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360502#comment-14360502
]
zhangduo commented on HBASE-13219:
--
{noformat}
grep -c ^\ t1
2067
grep -c ^\hconnection- t1
1917
{noformat}
Seems there are 2067 threads and 1917 of them are something like
hconnection-0x4f049d87-shared--pool16-t80. Maybe this is the problem.
I do not know where we create a thread with this pattern of name, need to dig
into the code. Is anyone familiar with this part of code?
Thanks.
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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360634#comment-14360634
]
Anoop Sam John commented on HBASE-13219:
Ram
Can check with PE tool option --oneCon=true?
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 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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358599#comment-14358599
]
ramkrishna.s.vasudevan commented on HBASE-13219:
For the 2nd one, may be there is some newly added configuration or something
that am missing that was added newly.
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358670#comment-14358670
]
zhangduo commented on HBASE-13219:
--
Set RpcClientFactory.CUSTOM_RPC_CLIENT_IMPL_CONF_KEY to RpcClientImpl.class and
try again?
And maybe we could try to get a thread dump then it is more clear if there are
thread leaks.
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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
[jira] [Commented] (HBASE-13219) Issues with PE tool in trunk
[
https://issues.apache.org/jira/browse/HBASE-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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(RetryingCallableV task, int callTimeout, int id) {
QueueingFutureV newFuture = new QueueingFutureV(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)
