apache.org
Subject: Re: [Worker Crashing] OutOfMemoryError: GC overhead limit execeeded
Yea we also didn't find anything related to this online.
Are you aware of any memory leaks in worker in 1.6.2 spark which might be
causing this ?
Do you know of any documentation which explains all the tasks t
t; *Sent:* Friday, March 24, 2017 9:15 AM
> *To:* Yong Zhang
> *Cc:* user@spark.apache.org
> *Subject:* Re: [Worker Crashing] OutOfMemoryError: GC overhead limit
> execeeded
>
> Thank you for the response.
>
> Yes, I am sure because the driver was working fine. Only 2 workers
: [Worker Crashing] OutOfMemoryError: GC overhead limit execeeded
Thank you for the response.
Yes, I am sure because the driver was working fine. Only 2 workers went down
with OOM.
Regards,
Behroz
On Fri, Mar 24, 2017 at 2:12 PM, Yong Zhang
mailto:java8...@hotmail.com>> wrote:
I am not 100% sur
Thank you for the response.
Yes, I am sure because the driver was working fine. Only 2 workers went
down with OOM.
Regards,
Behroz
On Fri, Mar 24, 2017 at 2:12 PM, Yong Zhang wrote:
> I am not 100% sure, but normally "dispatcher-event-loop" OOM means the
> driver OOM. Are you sure your workers
I am not 100% sure, but normally "dispatcher-event-loop" OOM means the driver
OOM. Are you sure your workers OOM?
Yong
From: bsikander
Sent: Friday, March 24, 2017 5:48 AM
To: user@spark.apache.org
Subject: [Worker Crashing] OutOfMemoryError: GC overhead limit