Re: Running TPCDSQueryBenchmark results in java.lang.OutOfMemoryError

Do you need more information? > On 23 May 2016, at 19:16, Ovidiu-Cristian MARCU > wrote: > > Yes, > > git log > commit dafcb05c2ef8e09f45edfb7eabf58116c23975a0 > Author: Sameer Agarwal > > Date: Sun May 22

Re: Running TPCDSQueryBenchmark results in java.lang.OutOfMemoryError

Yes, git log commit dafcb05c2ef8e09f45edfb7eabf58116c23975a0 Author: Sameer Agarwal Date: Sun May 22 23:32:39 2016 -0700 for #2 see my comments in https://issues.apache.org/jira/browse/SPARK-15078 > On 23 May 2016,

Re: Running TPCDSQueryBenchmark results in java.lang.OutOfMemoryError

Can you tell us the commit hash using which the test was run ? For #2, if you can give full stack trace, that would be nice. Thanks On Mon, May 23, 2016 at 8:58 AM, Ovidiu-Cristian MARCU < ovidiu-cristian.ma...@inria.fr> wrote: > Hi > > 1) Using latest spark 2.0 I've managed to run

Running TPCDSQueryBenchmark results in java.lang.OutOfMemoryError

Hi 1) Using latest spark 2.0 I've managed to run TPCDSQueryBenchmark first 9 queries and then it ends in the OutOfMemoryError [1]. What was the configuration used for running this benchmark? Can you explain the meaning of 4 shuffle partitions? Thanks! On my local system I use: