Re: [ANNOUNCE] Eric Badger is now a committer!

[Nandakumar Vadivelu]

Congrats Eric!

On 3/5/19, 10:50 PM, "Eric Payne"  wrote:

It is my pleasure to announce that Eric Badger has accepted an invitation 
to become a Hadoop Core committer.

Congratulations, Eric! This is well-deserved!

-Eric Payne



-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)

[Nandakumar Vadivelu]

Thanks Marton for all effort to make this release happen.

+1 (non-binding)

1. Verified Signature and Checksum
2. Build from Sources
3. Ran 5 node cluster using docker
4. Installed pseudo distributed cluster
5. Ran RPC and REST commands against the cluster
6. Verified SCM and OM UI

-Nanda

On 9/20/18, 3:19 AM, "Elek, Marton"  wrote:

Hi all,

After the recent discussion about the first Ozone release I've created 
the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha.

This release is alpha quality: it’s not recommended to use in production 
but we believe that it’s stable enough to try it out the feature set and 
collect feedback.

The RC artifacts are available from: 
https://home.apache.org/~elek/ozone-0.2.1-alpha-rc0/

The RC tag in git is: ozone-0.2.1-alpha-RC0 (968082ffa5d)

Please try the release and vote; the vote will run for the usual 5 
working days, ending on September 26, 2018 10pm UTC time.

The easiest way to try it out is:

1. Download the binary artifact
2. Read the docs at ./docs/index.html
3. TLDR; cd compose/ozone && docker-compose up -d


Please try it out, vote, or just give us feedback.

Thank you very much,
Marton

ps: At next week, we will have a BoF session at ApacheCon North Europe, 
Montreal on Monday evening. Please join, if you are interested, or need 
support to try out the package or just have any feedback.


-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 3.1.1 - RC0

[Nandakumar Vadivelu]

Thanks for all the hard work Wangda!
+1

* Verified pgp signatures
* Verified MD5 checksums
* Verified both source and binary releases
* Installed pseudo distributed cluster
* Verified hdfs filesystem commands
* Verified hdfs admin commands
* Verified hdfs snapshot commands
* Basic sanity check on NN UI

Issue found
* In "Browse the file system" under "Utilities" tab in NN UI, "Head the file" 
and "Tail the file" are not working.

-Nanda

On 8/3/18, 12:14 AM, "Wangda Tan"  wrote:

Hi folks,

I've created RC0 for Apache Hadoop 3.1.1. The artifacts are available here:

http://people.apache.org/~wangda/hadoop-3.1.1-RC0/

The RC tag in git is release-3.1.1-RC0:
https://github.com/apache/hadoop/commits/release-3.1.1-RC0

The maven artifacts are available via repository.apache.org at
https://repository.apache.org/content/repositories/orgapachehadoop-1139/

You can find my public key at
http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS

This vote will run 5 days from now.

3.1.1 contains 435 [1] fixed JIRA issues since 3.1.0.

I have done testing with a pseudo cluster and distributed shell job. My +1
to start.

Best,
Wangda Tan

[1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.1.1)
ORDER BY priority DESC

Re: 回复：[VOTE] Merge Storage Policy Satisfier (SPS) [HDFS-10285] feature branch to trunk

[Nandakumar Vadivelu]

+1 for the merge. Thanks for the work Uma et al.

-Nanda

On 8/7/18, 7:35 PM, "Vinayakumar B"  wrote:

+1

Great work guys.
-Vinay

On Tue, 7 Aug 2018, 7:20 pm Anu Engineer,  wrote:

> +1, Sorry for the late vote. Thanks for the perseverance and seeing this
> thru.
>
> --Anu
>
>
> On 8/7/18, 1:04 AM, "郑锴(铁杰)"  wrote:
>
> +1 for the work to be in. Thanks Uma and folks for the hard taking!
>
> When it's in, I'd suggest we use a more general name for the new
> daemon service. It'd be good to evolve and support more self-running admin
> functionalities incubated first there before doing it directly in 
NameNode.
>
> Regards,
> Kai
> --
> 发件人：Uma Maheswara Rao G 
> 发送时间：2018年8月1日(星期三) 14:38
> 收件人：hdfs-dev 
> 主 题：[VOTE] Merge Storage Policy Satisfier (SPS) [HDFS-10285] feature
> branch to trunk
>
> Hi All,
>
>
>
>  From the positive responses from JIRA discussion and no objections
> from
> below DISCUSS thread [1], I am converting it to voting thread.
>
>
>
>  Last couple of weeks we spent time on testing the feature and so far
> it is
> working fine. Surendra uploaded a test report at HDFS-10285:  [2]
>
>
>
>  In this phase, we provide to run SPS outside of Namenode only and as 
a
> next phase we continue to discuss and work on to enable it as Internal
> SPS
> as explained below. We have got clean QA report on branch and if there
> are
> any static tool comments triggered later while running this thread, we
> will
> make sure to fix them before merge. We committed and continue to
> improve
> the code on trunk. Please refer to HDFS-10285 for discussion details.
>
>
>
>  This has been a long effort and we're grateful for the support we've
> received from the community. In particular, thanks to Andrew Wang,
> Anoop
> Sam John, Anu Engineer, Chris Douglas, Daryn Sharp, Du Jingcheng , 
Ewan
> Higgs, Jing Zhao, Kai Zheng,  Rakesh R, Ramkrishna , Surendra Singh
> Lilhore
> , Thomas Demoor, Uma Maheswara Rao G, Vinayakumar, Virajith,  Wei 
Zhou,
> Yuanbo Liu. Without these members effort, this feature might not have
> reached to this state.
>
>
>
> To start with, here is my +1
>
> It will end on 6th Aug.
>
>
>
> Regards,
>
> Uma
>
> [1]  https://s.apache.org/bhyu
> [2]  https://s.apache.org/AXvL
>
>
> On Wed, Jun 27, 2018 at 3:21 PM, Uma Maheswara Rao G <
> hadoop@gmail.com>
> wrote:
>
> > Hi All,
> >
> >   After long discussions(offline and on JIRA) on SPS, we came to a
> > conclusion on JIRA(HDFS-10285) that, we will go ahead with External
> SPS
> > merge in first phase. In this phase process will not be running
> inside
> > Namenode.
> >   We will continue discussion on Internal SPS. Current code base
> supports
> > both internal and external option. We have review comments for
> Internal
> > which needs some additional works for analysis and testing etc. We
> will
> > move Internal SPS work to under HDFS-12226 (Follow-on work for SPS
> in NN)
> > We are working on cleanup task HDFS-13076 for the merge. .
> > For more clarity on Internal and External SPS proposal thoughts,
> please
> > refer to JIRA HDFS-10285.
> >
> > If there are no objections with this, I will go ahead for voting
> soon.
> >
> > Regards,
> > Uma
> >
> > On Fri, Nov 17, 2017 at 3:16 PM, Uma Maheswara Rao G <
> hadoop@gmail.com
> > > wrote:
> >
> >> Update: We worked on the review comments and additional JIRAs above
> >> mentioned.
> >>
> >> >1. After the feedbacks from Andrew, Eddy, Xiao in JIRA reviews, we
> >> planned to take up the support for recursive API support.
> HDFS-12291<
> >> https://issues.apache.org/jira/browse/HDFS-12291>
> >>
> >> We provided the recursive API support now.
> >>
> >> >2. Xattr optimizations HDFS-12225 >> he.org/jira/browse/HDFS-12225>
> >> Improved this portion as well
> >>
> >> >3. Few other review comments already fixed and committed
> HDFS-12214<
> >> https://issues.apache.org/jira/browse/HDFS-12214>
> >> Fixed the comments.
> >>
> >> We are continuing to test the feature and working so far well. Also
> we
> >> uploaded a combined patch and got the good QA report.

Re: [VOTE] Merge ContainerIO branch (HDDS-48) in to trunk

[Nandakumar Vadivelu]

+1

On 6/30/18, 3:44 AM, "Bharat Viswanadham"  wrote:

Fixing subject line of the mail.


Thanks,
Bharat



On 6/29/18, 3:10 PM, "Bharat Viswanadham"  
wrote:

Hi All,

Given the positive response to the discussion thread [1], here is the 
formal vote thread to merge HDDS-48 in to trunk.

Summary of code changes:
1. Code changes for this branch are done in the hadoop-hdds subproject 
and hadoop-ozone subproject, there is no impact to hadoop-hdfs.
2. Added support for multiple container types in the datanode code path.
3. Added disk layout logic for the containers to supports future 
upgrades.
4. Added support for volume Choosing policy to distribute containers 
across disks on the datanode.
5. Changed the format of the .container file to a human-readable format 
(yaml)


 The vote will run for 7 days, ending Fri July 6th. I will start this 
vote with my +1.

Thanks,
Bharat

[1] 
https://lists.apache.org/thread.html/79998ebd2c3837913a22097102efd8f41c3b08cb1799c3d3dea4876b@%3Chdfs-dev.hadoop.apache.org%3E




-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 3.0.3 (RC0)

[Nandakumar Vadivelu]

Hi Allen,
It will be helpful if we can get the correct steps, and also update the wiki.
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Release+Validation

Thanks,
Nanda

On 6/8/18, 12:17 AM, "Steve Loughran"  wrote:



> On 7 Jun 2018, at 18:01, Allen Wittenauer  
wrote:
> 
> 
>> On Jun 7, 2018, at 3:46 AM, Lokesh Jain  wrote:
>> 
>> Hi Yongjun
>> 
>> I followed Nanda’s steps and I see the same issues as reported by Nanda.
> 
> 
> This situation is looking like an excellent opportunity for PMC members 
to mentor people on how the build works since it’s apparent that three days 
later, no one has mentioned that those steps aren’t the ones to build the 
complete website and haven’t been since at least 2.4.

Actually, Yongjun has been really good at helping me get set up for a 2.7.7 
release, including "things you need to do to get GPG working in the docker 
image"

But yes, I would like to know those complete steps too

> 
> 
> 
> -
> To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
> 


-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 3.0.3 (RC0)

[Nandakumar Vadivelu]

Thanks Yongjun for all the hard work on this release.

- Verified signatures and checksums
- Tested both the binary and also built from source on a pseudo distributed 
cluster
- Verified filesystem shell commands
- Verified admin commands
- Tested snapshot feature
- Sanity check of NN and DN UI
- Verified site documentation

The following links in site documentation are broken
- Changelog and Release Notes
- Unix Shell API
- core-default.xml
- hdfs-default.xml
- hdfs-rbf-default.xml
- mapred-default.xml
- yarn-default.xml

Site documentation was generated using the below steps
- mvn site:site
- mkdir -p /tmp/site && mvn site:stage -DstagingDirectory=/tmp/site
- Browse to file:///tmp/site/hadoop-project/index.html.

Thanks,
Nanda

On 6/3/18, 8:55 AM, "Yongjun Zhang"  wrote:

Hi Gabor,

I got the git tag in, it's release-3.0.3-RC0. Would you please give it a
try?

It should correspond to

commit 37fd7d752db73d984dc31e0cdfd590d252f5e075
Author: Yongjun Zhang 
Date:   Wed May 30 00:07:33 2018 -0700

Update version to 3.0.3 to prepare for 3.0.3 release


Thanks,

--Yongjun

On Fri, Jun 1, 2018 at 4:17 AM, Gabor Bota  wrote:

> Hi Yongjun,
>
> Thank you for working on this release. Is there a git tag in the upstream
> repo which can be checked out? I'd like to build the release from source.
>
> Regards,
> Gabor
>
> On Fri, Jun 1, 2018 at 7:57 AM Shashikant Banerjee <
> sbaner...@hortonworks.com> wrote:
>
>> Looks like the link with the filter seems to be private. I can't see the
>> blocker list.
>> https://issues.apache.org/jira/issues/?filter=12343997
>>
>> Meanwhile , I will be working on testing the release.
>>
>> Thanks
>> Shashi
>> On 6/1/18, 11:18 AM, "Yongjun Zhang"  wrote:
>>
>> Greetings all,
>>
>> I've created the first release candidate (RC0) for Apache Hadoop
>> 3.0.3. This is our next maintenance release to follow up 3.0.2. It
>> includes
>> about 249
>> important fixes and improvements, among which there are 8 blockers.
>> See
>> https://issues.apache.org/jira/issues/?filter=12343997
>>
>> The RC artifacts are available at:
>> https://dist.apache.org/repos/dist/dev/hadoop/3.0.3-RC0/
>>
>> The maven artifacts are available via
>> https://repository.apache.org/content/repositories/
>> orgapachehadoop-1126
>>
>> Please try the release and vote; the vote will run for the usual 5
>> working
>> days, ending on 06/07/2018 PST time. Would really appreciate your
>> participation here.
>>
>> I bumped into quite some issues along the way, many thanks to quite a
>> few
>> people who helped, especially Sammi Chen, Andrew Wang, Junping Du,
>> Eddy Xu.
>>
>> Thanks,
>>
>> --Yongjun
>>
>>
>>



-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Re: [VOTE] Merge HDDS (HDFS-7240) *code* into trunk

[Nandakumar Vadivelu]

+1  (non-binding)

On 4/17/18, 5:19 AM, "Jitendra Pandey"  wrote:

Hi All,

   The community unanimously voted (https://s.apache.org/HDDSMergeResult) 
to adopt 
HDDS/Ozone as a sub-project of Hadoop, here is the formal vote for code 
merge.

Here is a quick summary of the code changes:

- As decided in the JIRA HDFS-10419, the project has been renamed to Hadoop 
Distributed Data Store or HDDS.
- HDDS becomes a sub-project of Hadoop.
- Added a Maven profile that disables HDDS compilation by default.
- The releases of HDDS will be independent of Hadoop and will have no 
impact to current Hadoop release process.
- We have made HDDS a loadable module.
- Cleaned up changes in HDFS/Hadoop Common to make sure HDDS does not 
impact current users of HDFS.

The vote will run for 7 days, I will start this vote with my +1.

Thanks
Jitendra


-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org




-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Re: [VOTE] Adopt HDSL as a new Hadoop subproject

[Nandakumar Vadivelu]

+1 (non-binding)

On 3/23/18, 8:23 AM, "dujunp...@gmail.com on behalf of 俊平堵" 
 wrote:

I think the proposal here is the right way to get consensus from each part
of community. +1 (binding)
Thanks Owen for driving this.


Thanks,

Junping

2018-03-21 2:20 GMT+08:00 Owen O'Malley :

> All,
>
> Following our discussions on the previous thread (Merging branch HDFS-7240
> to trunk), I'd like to propose the following:
>
> * HDSL become a subproject of Hadoop.
> * HDSL will release separately from Hadoop. Hadoop releases will not
> contain HDSL and vice versa.
> * HDSL will get its own jira instance so that the release tags stay
> separate.
> * On trunk (as opposed to release branches) HDSL will be a separate module
> in Hadoop's source tree. This will enable the HDSL to work on their trunk
> and the Hadoop trunk without making releases for every change.
> * Hadoop's trunk will only build HDSL if a non-default profile is enabled.
> * When Hadoop creates a release branch, the RM will delete the HDSL module
> from the branch.
> * HDSL will have their own Yetus checks and won't cause failures in the
> Hadoop patch check.
>
> I think this accomplishes most of the goals of encouraging HDSL 
development
> while minimizing the potential for disruption of HDFS development.
>
> The vote will run the standard 7 days and requires a lazy 2/3 vote. PMC
> votes are binding, but everyone is encouraged to vote.
>
> +1 (binding)
>
> .. Owen
>



-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

[Nandakumar Vadivelu]

+1 (non-binding)

 - Verified checksums of all tarballs
 - Build from source with java 1.8.0_102
 - Deployed a pseudo cluster
 - Verified HDFS shell commands
 - Ran basic HDFS sanity tests

Thanks Andrew for all the effort!

On 11/15/17, 3:04 AM, "Andrew Wang"  wrote:

Hi folks,

Thanks as always to the many, many contributors who helped with this
release. I've created RC0 for Apache Hadoop 3.0.0. The artifacts are
available here:

http://people.apache.org/~wang/3.0.0-RC0/

This vote will run 5 days, ending on Nov 19th at 1:30pm Pacific.

3.0.0 GA contains 291 fixed JIRA issues since 3.0.0-beta1. Notable
additions include the merge of YARN resource types, API-based configuration
of the CapacityScheduler, and HDFS router-based federation.

I've done my traditional testing with a pseudo cluster and a Pi job. My +1
to start.

Best,
Andrew