Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of yzhang@cloudera.com
 designates 209.85.216.181 as permitted sender)
MIME-Version: 1.0
Date: Mon, 17 Nov 2014 12:00:12 -0800
Message-ID: 
 <CAA0W1bRozFnmPrWB8+NwGtb9XzyGHeVererM533buTiFQbmprA@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Hadoop 2.6.0
From: Yongjun Zhang <yzhang@cloudera.com>
To: common-dev@hadoop.apache.org
Cc: "yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=001a1135234e2ac1150508136dbf

--001a1135234e2ac1150508136dbf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Suresh,

I did review HDFS-6833 and the patch Shinichi provided a while back. It's
not really directly related to replication factor. The problem reported
there is, DirectoryScanner tries to register with NN blocks already
scheduled to be deleted as regular blocks, due to the delay in block
removal at DN side. This is wrong, and caused extra cycle/bandwidth and it
should not happen. And the patch tries to fix that.

I think it's a good fix to have, but probably targetting at 2.6.1 would be
fine. Given that the fix is still pending a committer's review, it will
take some time and we should push on that. I do hope the fix can get in as
soon as possible though.

Would you please share with us the timeframe for 2.6.1, and I hope the
schedule will work with Tsuyoshi.

Thanks.

--Yongjun


On Mon, Nov 17, 2014 at 10:03 AM, Suresh Srinivas <suresh@hortonworks.com>
wrote:

> Tsuyoshi, thanks for bringing up HDFS-6833. However, given it is a bounda=
ry
> condition (and should not cause issues when for files with replication
> factor 3), we should perhaps target this into 2.6.1 and not block this
> release. Thoughts?
>
> On Mon, Nov 17, 2014 at 4:17 AM, Tsuyoshi OZAWA <ozawa.tsuyoshi@gmail.com=
>
> wrote:
>
> > +0(non-binding)
> >
> > HDFS-6833 is critical issue for us - could you help us to merge it into
> > 2.6?
> >
> > Thanks,
> > - Tsuyoshi
> >
> > On Sat, Nov 15, 2014 at 1:03 PM, Hitesh Shah <hitesh@apache.org> wrote:
> > > +1 (binding)
> > >
> > > Built Hadoop from source, compiled Tez against the hadoop jars pushed
> to
> > staging repo and ran a few example Tez jobs on a single node cluster.
> > >
> > > =E2=80=94 HItesh
> > >
> > >
> > > On Nov 13, 2014, at 3:08 PM, Arun C Murthy <acm@hortonworks.com>
> wrote:
> > >
> > >> Folks,
> > >>
> > >> I've created another release candidate (rc1) for hadoop-2.6.0 based =
on
> > the feedback.
> > >>
> > >> The RC is available at:
> > http://people.apache.org/~acmurthy/hadoop-2.6.0-rc1
> > >> The RC tag in git is: release-2.6.0-rc1
> > >>
> > >> The maven artifacts are available via repository.apache.org at
> > https://repository.apache.org/content/repositories/orgapachehadoop-1013=
.
> > >>
> > >> Please try the release and vote; the vote will run for the usual 5
> days.
> > >>
> > >> thanks,
> > >> Arun
> > >>
> > >>
> > >> --
> > >> CONFIDENTIALITY NOTICE
> > >> NOTICE: This message is intended for the use of the individual or
> > entity to
> > >> which it is addressed and may contain information that is
> confidential,
> > >> privileged and exempt from disclosure under applicable law. If the
> > reader
> > >> of this message is not the intended recipient, you are hereby notifi=
ed
> > that
> > >> any printing, copying, dissemination, distribution, disclosure or
> > >> forwarding of this communication is strictly prohibited. If you have
> > >> received this communication in error, please contact the sender
> > immediately
> > >> and delete it from your system. Thank You.
> > >
> >
> >
> >
> > --
> > - Tsuyoshi
> >
>
>
>
> --
> http://hortonworks.com/download/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity =
to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified th=
at
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediate=
ly
> and delete it from your system. Thank You.
>

--001a1135234e2ac1150508136dbf--