I would like to nominate YARN-3832 as 2.6.1 candidate which is critical and I also saw it happened recently on a 2.6.0 cluster. Hope this is not too late.
Thanks, Junping ________________________________________ From: Rich Haase <rha...@pandora.com> Sent: Thursday, August 06, 2015 1:52 AM To: mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org Subject: Re: Planning Hadoop 2.6.1 release +1 to add those fixes. Rich Haase | Sr. Software Engineer | Pandora m 303.887.1146 | rha...@pandora.com On 8/5/15, 11:42 AM, "Wangda Tan" <wheele...@gmail.com> wrote: >Can we add following two fixes to 2.6.1? > >https://issues.apache.org/jira/browse/YARN-2922 and >https://issues.apache.org/jira/browse/YARN-3487. > >They're not fatal issue, but they can cause lots of issue in a large >cluster. > >Thanks, >Wangda > > >On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee <sj...@apache.org> wrote: > >> See my later update in the thread. HDFS-7704 is in the list. >> >> Thanks, >> Sangjin >> >> On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli < >> vino...@hortonworks.com> wrote: >> >> > Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and >>is >> > not part of the candidate list. Removed HDFS-7916 from the list. >> > >> > Thanks >> > +Vinod >> > >> > > On Jul 24, 2015, at 6:32 PM, Sangjin Lee <sj...@apache.org> wrote: >> > > >> > > Out of the JIRAs we proposed, please remove HDFS-7916. I don't >>think it >> > > applies to 2.6. >> > > >> > > Thanks, >> > > Sangjin >> > >> > >>
