hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jing Zhao <j...@hortonworks.com>
Subject Re: [VOTE] Merge HDFS-5535 Rolling Upgrade Improvement
Date Fri, 28 Feb 2014 19:04:10 GMT
+1 for the merging.


On Fri, Feb 28, 2014 at 10:58 AM, Chris Nauroth <cnauroth@hortonworks.com>wrote:

> +1 for the merge.
>
> I just got caught up on the current state of the branch, and it looks good.
>  End user documentation is in place.  I deployed a cluster built from the
> branch, and then I used the documentation to test various scenarios of
> rolling upgrade, downgrade and rollback.  Everything worked as expected.
>  This looks ready to merge.
>
> Nice work, everyone!
>
> Chris Nauroth
> Hortonworks
> http://hortonworks.com/
>
>
>
> On Thu, Feb 27, 2014 at 7:02 PM, Kihwal Lee <kihwal@yahoo-inc.com> wrote:
>
> > +1
> >
> > > On Feb 25, 2014, at 3:42 PM, "Tsz Wo Sze" <szetszwo@yahoo.com> wrote:
> > >
> > > Hi hdfs-dev,
> > >
> > > We propose merging the HDFS-5535 branch to trunk.
> > >
> > > HDFS Rolling Upgrade is a feature to allow upgrading individual HDFS
> > daemons.  In Hadoop v2, HDFS supports highly-available (HA) namenode
> > services and wire compatibility. These two capabilities make it feasible
> to
> > upgrade HDFS without incurring HDFS downtime.  We make such improvement
> in
> > the HDFS-5535 branch.
> > >
> > > The HDFS-5535 branch is ready to be merged to trunk.  As this being
> > written, there are 48 subtasks in HDFS-5535; 44 subtasks are already
> > completed.  The core developments including feature development, unit
> tests
> > and user doc, are already done.  The merge patch posted a few ago already
> > passed Jenkins.  I will post a updated patch to trigger Jenkins again for
> > the latest code base.
> > >
> > > The remaining JIRAs are:
> > >
> > > HDFS-3225: Revist upgrade snapshots, roll back, finalize to enable
> > rolling upgrades (assigned to Sanjay)
> > > HDFS-6000: Avoid saving namespace when starting rolling upgrade
> > (assigned to Jing)
> > > HDFS-6013: add rollingUpgrade information to  latest UI (assigned to
> > Vinay)
> > > HDFS-6016: Update datanode replacement policy to make writes more
> robust
> > (assigned to Kihwal)
> > >
> > > HDFS-6000 will be committed soon.  All other issues are further
> > improvements which can be done after merge.
> > >
> > > The other remaining works are:
> > > - Revise the design doc
> > > - Post a test plan (Haohui is working on it.)
> > > - Execute the manual tests (Haohui and Fengdong will work on it.)
> > >
> > > The work was a collective effort of Nathan Roberts, Sanjay Radia,
> Suresh
> > Srinivas, Kihwal Lee, Jing Zhao, Arpit Agarwal, Brandon Li, Haohui Mai,
> > Vinayakumar B, Fengdong Yu, Chris Nauroth and Tsz-Wo Nicholas Sze, who
> have
> > proposed the design, worked on the code, reviewed patches, tested the
> > features and authored documentation.  We thank everyone that who has gave
> > us valuable comments and feedback on the feature.
> > >
> > > The vote runs for 7 days.  Here is my +1 on the merge.
> > >
> > > Thanks.
> > > Tsz-Wo
> >
>
> --
> 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 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.
>

-- 
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 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.

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