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 details.
> I believe one o
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 wrote:
