PS - I don't get this behaviour in all the cases. I did many runs of the
same job & i get this behaviour in around 40% of the cases.
Task 4 is the bottom row in the metrics table
Thank you,
Abhishek
e: abshkm...@gmail.com
p: 91-8233540996
On Tue, Feb 16, 2016 at 11:19 PM, Abhishek Modi wrote:
Darren: this is not the last task of the stage.
Thank you,
Abhishek
e: abshkm...@gmail.com
p: 91-8233540996
On Tue, Feb 16, 2016 at 6:52 PM, Darren Govoni wrote:
> There were some posts in this group about it. Another person also saw the
> deadlock on next to last or last stage task.
>
> I've
I meant to write 'last task in stage'.
Sent from my Verizon Wireless 4G LTE smartphone
Original message
From: Darren Govoni
Date: 02/16/2016 6:55 AM (GMT-05:00)
To: Abhishek Modi , user@spark.apache.org
Subject: RE: Unusually large deserialisation time
Darren:
Can you post link to the deadlock issue you mentioned ?
Thanks
> On Feb 16, 2016, at 6:55 AM, Darren Govoni wrote:
>
> I think this is part of the bigger issue of serious deadlock conditions
> occurring in spark many of us have posted on.
>
> Would the task in question be the past tas
I think this is part of the bigger issue of serious deadlock conditions
occurring in spark many of us have posted on.
Would the task in question be the past task of a stage by chance?
Sent from my Verizon Wireless 4G LTE smartphone
Original message
From: Abhishek Modi
