rretention/input/feature_6.0_20151001_20160531_behavior_201511_201604_summary/lenderId_feature_live
> > 50 > log_file
> >
> > executor 40 lost<--would it be due to
> this,
> > sometimes job may fail for the reason
> > ..
> &
og), but this is only information about
> killed container, not about the reasons why this stage took so much memory
>
> As I can see in your logs, failed step relates to shuffle operation, could
> you change your job to avoid massive shuffle operation?
>
> --
> WBR, Alexander
&
t; (yarn--nodemanager-.log), but this is only information about
> > killed container, not about the reasons why this stage took so much
> memory
> >
> > As I can see in your logs, failed step relates to shuffle operation,
> could
> > you change your job to avoid massive shuffl
.log), but this is only information about
> killed container, not about the reasons why this stage took so much memory
>
> As I can see in your logs, failed step relates to shuffle operation, could
> you change your job to avoid massive shuffle operation?
>
> --
> WBR, Ale
, Alexander From: Zhiliang Zhu
Sent: 17 июня 2016 г. 14:10
To: User; kp...@hotmail.com
Subject: Re: spark job automatically killed without rhyme or reason
Show original message
Hi Alexander,
is your yarn userlog just for the executor log ?
as for those logs seem a little difficult to exactly
;
Sent: 17 июня 2016 г. 14:10
To: User<mailto:user@spark.apache.org>;
kp...@hotmail.com<mailto:kp...@hotmail.com>
Subject: Re: spark job automatically killed without rhyme or reason
Show original message
Hi Alexander,
is your yarn userlog just for the executor log ?
as for those
n kill containers where spark tasks are executed. In this
situation, please check yarn userlogs for more information… --WBR, Alexander
From: Zhiliang Zhu
Sent: 17 июня 2016 г. 9:36
To: Zhiliang Zhu; User
Subject: Re: spark job automatically killed without rhyme or reason anyone
ever met th
more information… --WBR, Alexander
From: Zhiliang Zhu
Sent: 17 июня 2016 г. 9:36
To: Zhiliang Zhu; User
Subject: Re: spark job automatically killed without rhyme or reason anyone
ever met the similar problem, which is quite strange ...
On Friday, June 17, 2016 2:13 PM, Zhiliang Zhu
w
e spark tasks are executed. In this
situation, please check yarn userlogs for more information… --WBR, Alexander
From: Zhiliang Zhu
Sent: 17 июня 2016 г. 9:36
To: Zhiliang Zhu; User
Subject: Re: spark job automatically killed without rhyme or reason anyone
ever met the similar problem, which
n this
situation, please check yarn userlogs for more information… --WBR, Alexander
From: Zhiliang Zhu
Sent: 17 июня 2016 г. 9:36
To: Zhiliang Zhu; User
Subject: Re: spark job automatically killed without rhyme or reason anyone
ever met the similar problem, which is quite strange ...
On Frid
nt: 17 июня 2016 г. 9:36
To: Zhiliang Zhu<mailto:zchl.j...@yahoo.com>; User<mailto:user@spark.apache.org>
Subject: Re: spark job automatically killed without rhyme or reason
anyone ever met the similar problem, which is quite strange ...
On Friday, June 17, 2016 2:13 PM, Zhiliang
anyone ever met the similar problem, which is quite strange ...
On Friday, June 17, 2016 2:13 PM, Zhiliang Zhu
wrote:
Hi All,
I have a big job which mainly takes more than one hour to run the whole,
however, it is very much unreasonable to exit & finish to run midway (almost
80% of t
12 matches
Mail list logo
