Hey Wangda
Update: YARN-6592 has been merged to trunk.
Cheers
-Arun
On Wed, Jan 31, 2018 at 12:58 AM, Wangda Tan wrote:
> Hi Daniel,
>
> I agree, let's move the discussion to YARN-7292 and get it resolved before
> 3.1.0
>
> Thanks,
> Wangda
>
> On Wed, Jan 31, 2018 at 4:35 PM, Daniel Templeton
Hi Daniel,
I agree, let's move the discussion to YARN-7292 and get it resolved before
3.1.0
Thanks,
Wangda
On Wed, Jan 31, 2018 at 4:35 PM, Daniel Templeton
wrote:
> I added my comments on that JIRA. Looks like YARN-7292 is marked as a
> blocker for 3.1, and I would tend to agree with that.
I added my comments on that JIRA. Looks like YARN-7292 is marked as a
blocker for 3.1, and I would tend to agree with that. Let's see what we
can to do get profiles nailed down so that 3.1 can go forward.
Daniel
On 1/18/18 10:25 AM, Wangda Tan wrote:
Thanks Daniel,
We need to make a decisi
ma
>
>
>
> *From: *Wangda Tan
> *Date: *Tuesday, January 30, 2018 at 6:24 AM
> *To: *Uma Gangumalla
> *Cc: *"hdfs-...@hadoop.apache.org" , "
> yarn-...@hadoop.apache.org" , "
> common-dev@hadoop.apache.org" , "
> mapreduce-...@hado
; ,
"yarn-...@hadoop.apache.org" ,
"common-dev@hadoop.apache.org" ,
"mapreduce-...@hadoop.apache.org" , Vinod
Kumar Vavilapalli
Subject: Re: Hadoop 3.1.0 release discussion
Thanks for the update.
On Tue, Jan 30, 2018 at 4:51 PM, Gangumalla, Uma
mailto:uma.ganguma...@i
e will keep SPS off by
> default. So,
> > interested users only can enable explicitly.
> >
> >
> >
> > Regards,
> >
> > Uma
> >
> >
> >
> > *From: *Wangda Tan
> > *Date: *Friday,
uot;hdfs-...@hadoop.apache.org" , "
> yarn-...@hadoop.apache.org" , "
> common-dev@hadoop.apache.org" , "
> mapreduce-...@hadoop.apache.org" , Vinod
> Kumar Vavilapalli
> *Subject: *Re: Hadoop 3.1.0 release discussion
>
&
>
> Uma
>
>
>
> *From: *Wangda Tan
> *Date: *Friday, January 26, 2018 at 5:21 PM
> *To: *Uma Gangumalla
> *Cc: *"hdfs-...@hadoop.apache.org" , "
> yarn-...@hadoop.apache.org" , "
> common-dev@hadoop.apache.org" , "
> mapred
To: Uma Gangumalla
Cc: "hdfs-...@hadoop.apache.org" ,
"yarn-...@hadoop.apache.org" ,
"common-dev@hadoop.apache.org" ,
"mapreduce-...@hadoop.apache.org" , Vinod
Kumar Vavilapalli
Subject: Re: Hadoop 3.1.0 release discussion
Hi All,
Just a reminder about feat
Hi All,
Just a reminder about feature freeze date.
Feature freeze date for 3.1.0 release is Jan 30 PST (about 4 days from
today), If you've any features which live in a branch and targeted to
3.1.0, please reply this email thread. Ideally, we should finish branch
merging before feature freeze dat
Sure, Wangda.
Regards,
Uma
On 1/18/18, 10:19 AM, "Wangda Tan" wrote:
Thanks Uma,
Could you update this thread once the merge vote started?
Best,
Wangda
On Wed, Jan 17, 2018 at 4:30 PM, Gangumalla, Uma
wrote:
> HI Wangda,
>
> Thank you fo
Thanks Daniel,
We need to make a decision about this:
https://issues.apache.org/jira/browse/YARN-7292, I believe this is the JIRA
you mentioned correct? Please let me know if there's anything else. And
let's move the discussion on JIRA.
The good news is that resource profile is merged to trunk al
Thanks Uma,
Could you update this thread once the merge vote started?
Best,
Wangda
On Wed, Jan 17, 2018 at 4:30 PM, Gangumalla, Uma
wrote:
> HI Wangda,
>
> Thank you for the head-up mail.
> We are in the branch (HDFS-10285) and trying to push the tasks sooner
> before the deadline.
>
> Regar
What's the status on resource profiles? I believe there are still a
couple of open JIRAs to rethink some of the design choices.
Daniel
On 1/17/18 11:33 AM, Wangda Tan wrote:
Hi All,
Since we're fast approaching previously proposed feature freeze date (Jan
30, about 13 days from today). If yo
HI Wangda,
Thank you for the head-up mail.
We are in the branch (HDFS-10285) and trying to push the tasks sooner before
the deadline.
Regards,
Uma
On 1/17/18, 11:35 AM, "Wangda Tan" wrote:
Hi All,
Since we're fast approaching previously proposed feature freeze date (Jan
30,
Hi All,
Since we're fast approaching previously proposed feature freeze date (Jan
30, about 13 days from today). If you've any features which live in a
branch and targeted to 3.1.0, please reply this email thread. Ideally, we
should finish branch merging before feature freeze date.
Here's an upda
Hi all,
Congratulations on the 3.0.0-GA release!
As we discussed in the previous email thread [1], I'd like to restart 3.1.0
release plans.
a) Quick summary:
a.1 Release status
We started 3.1 release discussion on Sep 6, 2017 [1]. As of today, there’re
232 patches loaded on 3.1.0 alone [2], besi
17 matches
Mail list logo
