Hi HDFS dev,

Both HDFS-7081 and HDFS-7095 have been completed.  I have also merged HDFS-6584 
to branch-2.  The Archival Storage feature will be available in the coming 
Hadoop 2.6.0 release.  Thanks.

Tsz-Wo


On Friday, September 19, 2014 10:21 PM, Tsz Wo Sze <szets...@yahoo.com> wrote:
 

>
>
>Hi HDFS dev,
>
>
>The HDFS-6584 branch has been merged to trunk.  We will finish the following 
>two items before merging it to branch-2.
>
>
>- HDFS-7081  Add new DistributedFileSystem API for getting all the existing 
>storage policies
>- HDFS-7095  TestStorageMover often fails in Jenkins
>
>
>Thanks for all the great work!
>Tsz-Wo
>
>
>
>
>
>
>On Friday, September 19, 2014 6:19 AM, Tsz Wo Sze <szets...@yahoo.com> wrote:
> 
>
>>
>>
>>Hi HDFS dev,
>>
>>
>>We have four +1's  (Vinay, Jitendra, Arpit and me) and no -1's.  The VOTE 
>>passed.
>>
>>
>>PS: Sorry that my email box seems having some problem.  I somehow did not 
>>receive 
Arpit's VOTE and some other emails. The email I sent last time (forwarded 
below) did not go out.
>>
>>
>>
>>Thanks everyone.
>>Tsz-Wo
>>
>>
>>
>>
>>
>>
>>On Tuesday, September 16, 2014 11:20 PM, Tsz Wo Sze <szets...@yahoo.com> 
>>wrote:
>> 
>>
>>>
>>>
>>>Hi HDFS dev,
>>>
>>>
>>>We have three binding +1's (Vinay, Jitendra and me) and no -1's.  The VOTE 
>>>passed.
>>>
>>>
>>>Thanks everyone.
>>>Tsz-Wo
>>>
>>>
>>>
>>>On Monday, September 8, 2014 4:03 PM, Nate Payne <npa...@cardinalpath.com> 
>>>wrote:
>>> 
>>>
>>>>
>>>>
>>>>+1. Great work everyone.
>>>>
>>>>On Sun, Sep 7, 2014
 at 11:17 PM, Jitendra Pandey <jiten...@hortonworks.com>
>>>>wrote:
>>>>
>>>>> +1. Great work by Nicholas and Jing.
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 8:09 PM, Vinayakumar B <vinayakum...@apache.org>
>>>>> wrote:
>>>>>
>>>>> > I have closely observed all work done in this. This featute is very
>>>>> > important for the
 storage only problems.
>>>>> >
>>>>> > Major work done by
 Nicholas and later Jing.
>>>>> >
>>>>> > Thanks to everyone who has participated in this.
>>>>> >
>>>>> > I feel the code is in good state to be merged to trunk.
>>>>> > +1 for the merge.
>>>>> >
>>>>> > Regards,
>>>>> > Vinay
>>>>> > On Sep 8, 2014 1:29 AM, "Tsz Wo Sze" <szets...@yahoo.com.invalid> wrote:
>>>>> >
>>>>> > > Hi HDFS dev,
>>>>> > >
>>>>> > > We would like to propose merging the development branch
>>>>> > > HDFS-6584 back to trunk.
>>>>> > >
>>>>> > > The work of HDFS-6584 is to support Archival Storage in
>>>>>
 > > HDFS.  Hadoop needs a solution to
>>>>> > > decouple growing storage capacity from compute capacity. Nodes with
>>>>> > higher
>>>>> > > density and less expensive storage with low compute power are becoming
>>>>> > > available and can be used as cold storage in the clusters. Based on
>>>>> > > policy, the
>>>>> > > data from hot can be moved to the cold. Adding more nodes to the cold
>>>>> > > storage
>>>>> > > can grow the storage independent of the compute capacity in the
>>>>> cluster.
>>>>> > >
>>>>> > > The Archival
 Storage feature introduces a new concept of
>>>>> > > storage policies (Hot, Warm, Cold) to HDFS and allows files to be
>>>>> stored
>>>>> > in
>>>>> > > different storage medias (DISK, ARCHIVE) according to the storage
>>>>> policy.
>>>>> > > A new data migration tool is added for
>>>>> > > archiving data.  For more details, please
>>>>> > > see the design doc posted in HDFS-6584.
>>>>> > >
>>>>> > > There are currently 22 sub-tasks in HDFS-6584.  The main feature of
>>>>> > > HDFS-6584 is implemented
>>>>> > > and tested.  The remaining work is adding
>>>>> > > user documentation, adding a test plan doc, adding more tests and
>>>>> fixing
>>>>> > > some
>>>>> > > minor bugs.  We will finish all of the
>>>>> > > remaining work before merging the branch to trunk.
>>>>> > >
>>>>> > > The contributors of this work include Jing Zhao, Arpit
>>>>> > > Agarwal, Vinayakumar B, Suresh Srinivas, Sanjay Radia, Jitendra 
>>>>> > > Pandey,
>>>>> > > Haohui
>>>>> > > Mai and Tsz-Wo Nicholas Sze.  We thank
>>>>> > > the community
 for giving valuable comments and feedbacks on the design
>>>>> of
>>>>> > > this
>>>>> > > work.
>>>>> > >
>>>>> > > The vote will last for 7 days.  Of course, I am +1 on it.
>>>>> > >
>>>>> > > Regards,
>>>>> > > Tsz-Wo
>>>>> > >
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> <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 
>>>>> 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.
>>>>>
>>>>
>>>>
>>>>
>>>>-- 
>>>>Nathaniel Payne
>>>>Senior Data Architect
>>>>phone +1.778.374.3004 x236
>>>>web CardinalPath.com
>>>><http://www.cardinalpath.com/?utm_campaign=cp-personal&utm_source=npayne&utm_medium=email&utm_content=signature>
>>>>
>>>>-- 
>>>>
>>>>
>>>>Research shows that organizations with high online analytics maturity 
>>>><http://www.cardinalpath.com/services/online-analytics-maturity-model/assessment/?utm_source=footer&utm_medium=email&utm_campaign=cp-personal&utm_content=signature>
>>>> 
>>>>get better ROI from their digital marketing and analytics investments. Not 
>>>>sure what your organization's analytics maturity is? Do you want to see how 
>>>>you compare to over 900 companies
 worldwide? Take the Online Analytics 
>>>>Maturity Assessment (OAMA) 
>>>><http://www.cardinalpath.com/services/online-analytics-maturity-model/assessment/?utm_source=footer&utm_medium=email&utm_campaign=cp-personal&utm_content=signature>
>>>> 
>>>>and find out
 now! 
>>>>
>>>>This email, including any attachments, is for the sole use of the intended 
>>>>recipient and may contain confidential information. If you are not the 
>>>>intended recipient, please immediately notify us by reply email or by 
>>>>telephone, delete this email and destroy any copies. Thank you
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Reply via email to