Re: new error for me

2014-10-03 Thread Akhil Das
I used to face this while running it on a single node machine and when i allocate more memory for the executor. (ie, my machine was 28Gb memory and i allocated 26Gb for the executor, dropping the memory from 26 to 20Gb solved my issue.). If you are seeing an executor lost exception then you can try

Re: new error for me

2014-10-02 Thread jamborta
have you found a solution this problem? (or at least a cause) thanks, -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/new-error-for-me-tp10378p15655.html Sent from the Apache Spark User List mailing list archive at Nabble.com. -

Re: new error for me

2014-07-24 Thread phoenix bai
I am currently facing the same problem. error snapshot as below: 14-07-24 19:15:30 WARN [pool-3-thread-1] SendingConnection: Error finishing connection to r64b22034.tt.net/10.148.129.84:47525 java.net.ConnectException: Connection timed out at sun.nio.ch.SocketChannelImpl.checkConnect(Nativ