Re: [VOTE] Apache Hadoop Ozone 1.0.0 RC1

+1 (binding) 1. Verified signatures 2. Built from source 3. deployed with docker 4. tested with basic s3 apis. On Tue, Aug 25, 2020 at 7:01 AM Sammi Chen wrote: > RC1 artifacts are at: > https://home.apache.org/~sammichen/ozone-1.0.0-rc1/ >

Re: [DISCUSS] Feature branch for HDFS-14978 In-place Erasure Coding Conversion

+1 for the feature branch. On Thu, Jan 23, 2020 at 1:34 PM Wei-Chiu Chuang wrote: > Hi we are working on a feature to improve Erasure Coding, and I would like > to seek your opinion on creating a feature branch for it. (HDFS-14978 > ) > > Reason

Re: [DISCUSS] Ozone 0.4.2 release

+1 > On Dec 7, 2019, at 9:13 AM, Arpit Agarwal > wrote: > > +1 > > > >> On Dec 6, 2019, at 5:25 PM, Dinesh Chitlangia wrote: >> >> All, >> Since the Apache Hadoop Ozone 0.4.1 release, we have had significant >> bug fixes towards performance & stability. >> >> With that in mind, 0.4.2

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

The immediate problem we need to fix is to prevent github updates from spamming the dev mailing list. Might make sense to just have a separate issues@ mailing list and point github to that? On Sun, Oct 27, 2019 at 10:12 PM Dinesh Chitlangia wrote: > +1 > > -Dinesh > > > > > On Sun, Oct 27,

Re: [DISCUSS] Remove Ozone and Submarine from Hadoop repo

+1 On Thu, Oct 24, 2019 at 6:42 PM Ayush Saxena wrote: > Thanx Akira for putting this up. > +1, Makes sense removing. > > -Ayush > > > On 25-Oct-2019, at 6:55 AM, Dinesh Chitlangia > > > wrote: > > > > +1 and Anu's approach of creating a tag makes sense. > > > > Dinesh > > > > > > > > > >> On

Re: [VOTE] - HDDS-4 Branch merge

+1 (binding) On 1/11/19, 10:26 AM, "Ajay Kumar" wrote: +1 (non-binding) On 1/11/19, 7:40 AM, "Anu Engineer" wrote: Since I have not heard any concerns, I will start a VOTE thread now. This vote will run for 7 days and will end on Jan/18/2019 @ 8:00 AM PST.

Re: [Discuss] - HDDS-4 Branch merge

+1, This is a great effort and another milestone in making HDDS and Ozone ready for enterprises. On 1/7/19, 5:10 PM, "Anu Engineer" wrote: Hi All, I would like to propose a merge of HDDS-4 branch to the Hadoop trunk. HDDS-4 branch implements the security work for HDDS and

Re: [VOTE] Release Apache Hadoop Ozone 0.3.0-alpha (RC1)

+1 (binding) Built from source. Ran smoke tests. On 11/19/18, 9:02 AM, "Anu Engineer" wrote: +1. (Binding) Thanks for getting this release done. Verified the signatures and S3 Gateway. --Anu On 11/16/18, 5:15 AM, "Shashikant Banerjee" wrote:

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

+1 On 6/29/18, 3:14 PM, "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

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

clean up the unused classes, fix old integration tests and continue testing the changes. Thanks to Hanisha Koneru, Arpit Agarwal, Anu Engineer, Jitendra Pandey, Xiaoyu Yao, Ajay Kumar, Mukul Kumar Singh, Marton Elek and Shashikant Banerjee for their contributions in design,

Re: [VOTE] Merging branch HDFS-7240 to trunk

wen O'Malley <owen.omal...@gmail.com>, Daryn Sharp <da...@oath.com.invalid>, Jitendra Pandey <jiten...@hortonworks.com>, hdfs-dev <hdfs-...@hadoop.apache.org>, "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>, "yarn-...@had

[VOTE] Merging branch HDFS-7240 to trunk

Dear folks, We would like to start a vote to merge HDFS-7240 branch into trunk. The context can be reviewed in the DISCUSSION thread, and in the jiras (See references below). HDFS-7240 introduces Hadoop Distributed Storage Layer (HDSL), which is a distributed,

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

Hi Konstantin, Thank you for taking out time to review ozone. I appreciate your comments and questions. > There are two main limitations in HDFS > a) The throughput of Namespace operations. Which is limited by the >number of RPCs the NameNode can handle > b) The number of objects (files +

Re: 答复: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

I have filed https://issues.apache.org/jira/browse/HDFS-12697 to ensure ozone stays disabled in a secure environment. Since ozone is disabled by default and will not come with security on, it will not expose any new attack surface in a Hadoop deployment. Ozone security effort will need a

Re: Why there are so many revert operations on trunk?

Colin raised the -1 demanding a design document. The document was added the very next day. There were constructive discussions on the design. There was a demand for listenable future or futures with callback, which was accepted to accommodate. Rest of the work having been completed, there was

Re: Thinking ahead to hadoop-2.6

I also believe its worth a week's wait to include HDFS-6584 and HDFS-6581 in 2.6. On Wed, Sep 24, 2014 at 3:28 PM, Suresh Srinivas sur...@hortonworks.com wrote: Given some of the features are in final stages of stabilization, Arun, we should hold off creating 2.6 branch or building an RC by a

Re: [PROPOSAL] change in bylaws to remove Release Plan vote

+1 On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote: +1 thanks Matt. On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote: Hi all, This has been a side topic in several email threads recently. Currently we have an ambiguity. We have a tradition

Re: [VOTE] Release hadoop-2.0.3-alpha

Downloaded, verified checksums, installed and did basic verification. +1 (binding) On Thu, Feb 7, 2013 at 11:54 AM, Karthik Kambatla ka...@cloudera.comwrote: +1 (non-binding) Downloaded src tar ball, built binary tar ball, ran a couple of sample MR jobs on a pseudo-dist cluster. On Thu,

Re: [VOTE] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack

+1, +1, +1 On Fri, Nov 30, 2012 at 5:40 AM, Radim Kolar h...@filez.com wrote: inline ant scripts =0. Ant's versioning is stricter; you can pull down the exact Jar versions, and some of us in the Ant team worked very hard to get it going everywhere. You don't gain anything by going to

Re: [PROPOSAL] 1.1.1 and 1.2.0 scheduling

+1 On Fri, Nov 9, 2012 at 9:52 AM, Matt Foley ma...@apache.org wrote: Hi all, Hadoop 1.1.0 came out on Oct 12. I think there's enough interest to do a maintenance release with some important patches. I propose to code freeze branch-1.1 a week from today, Fri 16 Nov, and have a 1.1.1

Re: [VOTE] Hadoop-1.0.1 Release Candidate 1

+1 for 1.0.1 Verified checksums and ran wordcount on single node cluster. On Tue, Feb 21, 2012 at 10:49 AM, Devaraj Das d...@hortonworks.com wrote: +1 Downloaded the tar ball and stood up a single-node cluster. Ran a sleep job. On Feb 14, 2012, at 2:29 PM, Matt Foley wrote: Hi all,

Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

The trunk, 206 patches for HDFS-2246 have been committed. I think it makes sense to commit it to 205.1 as well for following reasons (most of it has already been mentioned) a) We intended this patch for 205, but couldn't finish in time. Now that 205.1 branch is still not cut, we could get this in.

Re: [VOTE] 0.20.205.0 Release Candidate 2

I deployed on 5 node cluster with security turned on and ran mapreduce jobs. Verified md5 signature of the rpm. +1. On Fri, Oct 7, 2011 at 5:10 PM, Matt Foley ma...@apache.org wrote: Many thanks to the community members who tried out RC1, and found several critical or blocker bugs. These