Sorry for the noise, It's my bad...I have worked it out now.
At 2015-08-26 13:20:57, Todd bit1...@163.com wrote:
I think the answer is No. I only see such message on the console..and #2 is the
thread stack trace。
I am thinking is that in Spark SQL Perf forks many dsdgen process to generate
Mind sharing how you fixed the issue ?
Cheers
On Aug 26, 2015, at 1:50 AM, Todd bit1...@163.com wrote:
Sorry for the noise, It's my bad...I have worked it out now.
At 2015-08-26 13:20:57, Todd bit1...@163.com wrote:
I think the answer is No. I only see such message on the
Increase the number of executors, :-)
At 2015-08-26 16:57:48, Ted Yu yuzhih...@gmail.com wrote:
Mind sharing how you fixed the issue ?
Cheers
On Aug 26, 2015, at 1:50 AM, Todd bit1...@163.com wrote:
Sorry for the noise, It's my bad...I have worked it out now.
At 2015-08-26 13:20:57,
The error in #1 below was not informative.
Are you able to get more detailed error message ?
Thanks
On Aug 25, 2015, at 6:57 PM, Todd bit1...@163.com wrote:
Thanks Ted Yu.
Following are the error message:
1. The exception that is shown on the UI is :
Exception in thread Thread-113
I think the answer is No. I only see such message on the console..and #2 is the
thread stack trace。
I am thinking is that in Spark SQL Perf forks many dsdgen process to generate
data when the scalafactor is increased which at last exhaust the JVM
When thread exception is thrown on the console
Looks like you were attaching images to your email which didn't go through.
Consider using third party site for images - or paste error in text.
Cheers
On Tue, Aug 25, 2015 at 4:22 AM, Todd bit1...@163.com wrote:
Hi，
The spark sql perf itself contains benchmark data generation. I am using
Hi，
The spark sql perf itself contains benchmark data generation. I am using spark
shell to run the spark sql perf to generate the data with 10G memory for both
driver and executor.
When I increase the scalefactor to be 30,and run the job, Then I got the
following error:
When I jstack it to
Thanks Ted Yu.
Following are the error message:
1. The exception that is shown on the UI is :
Exception in thread Thread-113 Exception in thread Thread-126 Exception in
thread Thread-64 Exception in thread Thread-90 Exception in thread
Thread-117 Exception in thread Thread-80 Exception in
