Re: strange behavior of spark 2.1.0

Thank you for replying. Actually there is no any message coming during the exception. And there is no OOME in any executor. What I am suspecting it might be caused by AWL. > On Apr 2, 2017, at 5:22 AM, Timur Shenkao wrote: > > Hello, > It's difficult to tell without

Re: strange behavior of spark 2.1.0

Hello, It's difficult to tell without details. I believe one of the executors dies because of OOM or some Runtime Exception (some unforeseen dirty data row). Less probable is GC stop-the-world pause when incoming message rate increases drastically. On Saturday, April 1, 2017, Jiang Jacky

strange behavior of spark 2.1.0

Hello, Guys I am running the spark streaming in 2.1.0, the scala version is tried on 2.11.7 and 2.11.4. And it is consuming from JMS. Recently, I have get the following error *"ERROR scheduler.ReceiverTracker: Deregistered receiver for stream 0: Stopped by driver"* *This error can be occurred