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: [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] 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] 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-...@hadoop.apache.org" <common-...@hadoop.apache.org>, "yarn-dev@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: [DISCUSS] Change by-laws on release votes: 5 days instead of 7

+1, sounds good! On Mon, Jun 23, 2014 at 12:02 PM, Andrew Wang andrew.w...@cloudera.com wrote: +1 here as well, let's do a vote thread (for 7 days, maybe for the last time!) On Mon, Jun 23, 2014 at 11:46 AM, Vinod Kumar Vavilapalli vino...@apache.org wrote: This seems reasonable, +1.