hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Srinivas <sur...@hortonworks.com>
Subject Re: VOTE: HDFS-347 merge
Date Fri, 05 Apr 2013 04:40:03 GMT
> We usually conclude the last VOTE before starting a new one.  Otherwise,
> people may be confused between the VOTEs.  (In case you don't know our
> convention.  Please check with someone before starting a VOTE.  Thanks.)
> -1
> * The previous VOTE started by Colin has not been concluded.

Nicholas, given that the two voting threads are far apart in time, lets
keep this voting thread alive. So please consider withdrawing -1 on the
basis of this technical reason.

> * The branch is not ready.  The code misuses DataTransferProtocol.
> Documentation of the new conf properties are missing.  Also, the code in
> the branch needs to be polished.  See HDFS-347 and HDFS-4661 for more
> details.

Do you think these cannot be worked on trunk. I think waiting for all the
things complete in a feature branch might slowdown feature development. I
think some of these issues can be addressed in trunk. We could also
consider waiting for all the issues that you have brought up to be
addressed before merging it to the branch-2. Please do post a comment on
HDFS-347 on which of the issues should be addressed before merging to

> Tsz-Wo
> ________________________________
>  From: Colin McCabe <cmccabe@alumni.cmu.edu>
> To: hdfs-dev@hadoop.apache.org
> Sent: Tuesday, April 2, 2013 7:32 AM
> Subject: VOTE: HDFS-347 merge
> Hi all,
> I think it's time to merge the HDFS-347 branch back to trunk.  It's been
> under
> review and testing for several months, and provides both a performance
> advantage, and the ability to use short-circuit local reads without
> compromising system security.
> Previously, we tried to merge this and the objection was brought up that we
> should keep the old, insecure short-circuit local reads around so that
> platforms for which secure SCR had not yet been implemented could use it
> (e.g. Windows).  This has been addressed-- see HDFS-4538 for details.
> Suresh has also volunteered to maintain the insecure SCR code until secure
> SCR can be implemented for Windows.
> Please cast your vote by EOD Monday 4/8.
> best,
> Colin


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message