Re: [VOTE] Release Apache Hadoop 2.7.3 RC0

I noticed two issues: (1) I ran hadoop checknative, but it seems the binary tarball was not compiled with native library for Linux. On the contrary, the Hadoop built from source tarball with maven -Pnative can find the native libraries on the same host. (2) I noticed that the release dates in CHA

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/ppc64le

It seems many tests are failing after HADOOP-13514. The failed tests are reproducible locally. > On Oct 25, 2016, at 11:53 AM, Apache Jenkins Server > wrote: > > For more details, see > https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/135/ > > [Oct 24, 2016 1:28:44 PM] (kihwal

Re: [VOTE] Release Apache Hadoop 2.8.0 (RC3)

-2.8.0-src.tar.gz is 33MB comparing to hadoop-2.7.3-src.tar.gz which is 18MB. So probably it’s the amount of changes made into Hadoop 2.8 makes such difference in size. Regards, Wei-Chiu Chuang > On Mar 21, 2017, at 9:39 AM, Akira Ajisaka wrote: > > Thanks Junping! > &

Re: HADOOP-14316: Switching from Findbugs to Spotbugs

Hi Allen, That sounds scary. Would you mind to share the list of bugs that spotbugs found? Sounds like some of them may warrant new blockers jiras for Hadoop 3. Thank you, Wei-Chiu Chuang > On Apr 19, 2017, at 10:44 AM, Allen Wittenauer > wrote: > > HADOOP-14316 signature.asc

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

Hi, I'm sorry coming to this vote late. Daryn mentioned in HDFS-12136 that HDFS-11160 has a performance regression at DataNode due to the way it locks dataset lock. HDFS-11160 is in Hadoop 2.7.4.

Re: [DISCUSS] Apache Hadoop 2.7.5 Release Plan

Hi Konstantin, Thanks for initiating the release effort. I am marking HDFS-12641 as a blocker for Hadoop 2.7.5 because during our internal testing for CDH we found a regression in HDFS-11445 that was fixed by HDFS-11755 (technically not a real reg

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

@vinod I followed your command but I could not reproduce your problem. [weichiu@storage-1 hadoop-3.0.0-src]$ ls -al hadoop-common-project/hadoop-c ommon/target/hadoop-common-3.0.0.tar.gz -rw-rw-r-- 1 weichiu weichiu 37052439 Nov 20 21:59 hadoop-common-project/hadoop-common/target/hadoop-common-3.0

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

Hi Andrew, thanks the tremendous effort. I found an empty "patchprocess" directory in the source tarball, that is not there if you clone from github. Any chance you might have some leftover trash when you made the tarball? Not wanting to nitpicking, but you might want to double check so we don't sh

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

cess, > and it looks empty to me. We should still file a create-release JIRA to fix > this, but I think this is not a blocker. Would you agree? > > Best, > Andrew > > On Tue, Dec 12, 2017 at 9:44 AM, Wei-Chiu Chuang > wrote: > >> Hi Andrew, thanks the treme

Re: Apache Hadoop 2.9.1 Release Plan

Sorry Sammi I was late to this thread. Please considering incorporating HDFS-11915. Sync rbw dir on the first hsync() to avoid file lost on power failure. I thought it was already in 2.9.1 but turns out it didn't land. The cherry pick to branch-2.9 is conflict free. On Mon, Apr 2, 2018 at 4:34 AM,

Re: Apache Hadoop 2.9.1 Release Plan

you help to cherry-pick it to both branch-2.9 and branch-2.9.1? > > > Thanks, > Sammi > > -Original Message- > From: Wei-Chiu Chuang [mailto:weic...@cloudera.com] > Sent: Thursday, April 5, 2018 1:30 AM > To: Chen, Sammi > Cc: hdfs-dev ; mapreduce-dev@hadoop.apach

Re: Apache Hadoop 2.9.1 Release Plan

Done. Both HDFS-11915 and HDFS-13364 are in branch-2.9 and branch-2.9.1. Thank you Sammi for driving 2.9.1 release On Fri, Apr 6, 2018 at 10:14 AM, Wei-Chiu Chuang wrote: > >1. > Looks like: >2. HDFS-13347 <https://issues.apache.org/jira/browse/HDF

Re: Apache Hadoop 3.0.3 Release plan

Thanks Yongjun for driving 3.0.3 release! IMHO, could we consider adding YARN-7190 into the list? I understand that it is listed as an incompatible change, however, because of this bug, HBase considers the entire Hadoop 3.0.x line not production re

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

I'm sorry I come to this thread late. Anu commented on INFRA-16727 saying he reverted the commit. Do we still need the vote? Thanks On Thu, Jul 5, 2018 at 2:47 PM Rohith Sharma K S wrote: > +1 > > On 5 July 2018 at 14:37, Subru Krishnan wrote: > > > Folks, > > > > There was a merge commit acci

Re: Hadoop 3.2 Release Plan proposal

Thanks Sunil G for driving the release, I filed HADOOP-15866 for a compat fix. If any one has cycle please review it, as I think it is needed for 3.2.0. On Thu, Oct 18, 2018 at 4:43 AM Sunil G wrote: > Hi Folks, > > As we previously communicat

Re: Update guava to 27.0-jre in hadoop-project

+1 I watched Gabor working on this and this is a very comprehensive, which also includes testing in downstreamers (HBase and Hive). So very good work. Thanks! On Wed, Apr 3, 2019 at 3:41 AM Steve Loughran wrote: > I am taking silence as happiness here. > > +1 to the patch > > On Tue, Apr 2, 20

Re: [DISCUSS] A unified and open Hadoop community sync up schedule?

Thanks Wangda, I just like to make a correction -- the .ics calendar file says the first Wednesday for HDFS/cloud connector is in Mandarin whereas on the gdoc is to host it on the third Wednesday. On Tue, Jun 18, 2019 at 5:29 PM Wangda Tan wrote: > Hi Folks, > > I just updated doc: > > https://

HDFS-13287 broke the build; reverted

Sorry for the cross-post. If you find your build breaks, it's on me. I committed HDFS-13287 which resulted in compilation error in trunk/branch-3.2/branch-3.1. The commit has since been reverted. Thanks Akira for identifying the issue!

[DISCUSS] Prefer Github PR Integration over patch in JIRA

Historically, Hadoop developers create patches and attache them to JIRA, andthen the Yetus bot runs precommit against the patch in the JIRA. The Github PR is more convenient for code review and less hassle for committers to merge a commit. I am proposing for the community to prefer Github PR over

[DISCUSS] EOL 2.8 or another 2.8.x release?

The last 2.8 release (2.8.4) was made in the last May, more than a year ago. https://hadoop.apache.org/old/releases.html How do folks feel about the fate of branch-2.8? During the last community meetup in June, it sounds like most users are still on 2.8 or even 2.7, so I don't think we want to aba

Re: [DISCUSS] EOL 2.8 or another 2.8.x release?

My bad -- Didn't realize I was looking at the old Hadoop page. Here's the correct list of releases. https://hadoop.apache.org/releases.html On Thu, Jul 25, 2019 at 12:49 AM 张铎(Duo Zhang) wrote: > IIRC we have a 2.8.5 release? > > On the download page: > > 2.8.5 2018 S

Unassigned Hadoop jiras with patch available

I am using this jira filter to find jiras with patch available but unassigned. https://issues.apache.org/jira/issues/?filter=12346814&jql=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2CSUBMARINE)%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20assignee%20%3D%20EMPTY%20ORDER%20B

Re: Unassigned Hadoop jiras with patch available

%20updated%20DESC On Wed, Jul 31, 2019 at 3:02 PM Wei-Chiu Chuang wrote: > I am using this jira filter to find jiras with patch available but > unassigned. > > https://issues.apache.org/jira/issues/?filter=12346814&jql=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2C

Re: Unassigned Hadoop jiras with patch available

I assigned all jiras with patch available that are created since 2019. If you have jiras that you are actively working on that you can't assign to yourself, please let me know. On Wed, Jul 31, 2019 at 3:11 PM Wei-Chiu Chuang wrote: > I was told the filter is private. I am sorry. >

Please file a JIRA for your PR

The Hadoop community welcome your patch contribution, and like increasingly patches are submitted via GitHub Pull Requests. That is great, as it reduces the friction to review code & commit code. However, please make sure to file a jira for your PR, as described in the How to Contribute

Revert of HDFS-12914 breaks the branch-2

Heads up, My bad. This is becoming a mess. For the context, HDFS-12914 in branch-2 has a test failure, so I reverted it. But HDFS-13898 used a helper method (BlockManager#setBlockManagerForTesting()) added by HDFS-12914, so the revert breaks the build. Here's what I propose: (1) File a new Jira

Re: Unassigned Hadoop jiras with patch available

Interestingly enough, I think I can create new wiki, but I don't see a button to edit existing wiki. On Thu, Aug 15, 2019 at 6:24 AM Masatake Iwasaki < iwasak...@oss.nttdata.co.jp> wrote: > Hi Wei-Chiu Chuang, > > Thanks for doing this and sorry for late reply. > &g

Re: [DISCUSS] Hadoop-3.2.1 release proposal

Hi Rohith, Thanks for initiating this. I want to bring up one blocker issue: HDFS-13596 (NN restart fails after RollingUpgrade from 2.x to 3.x) This should be a blocker for all active Hadoop 3.x releases: 3.3.0, 3.2.1, 3.1.3. Hopefully we can get

Re: Make EOL branches to public?

+1 I feel like one year of inactivity is a good sign that the community is not interested in the branch any more. On Fri, Aug 16, 2019 at 3:14 AM Wangda Tan wrote: > Hi folks, > > Want to hear your thoughts about what we should do to make some branches > EOL. We discussed a couple of times befor

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

This is starting to diverge from the original topic :) But I would like to say (1) If we are treating branch-2/2.0 as the final, last 2.x release, we should be proactive in updating dependencies. I did a quick search and found a lot of dependencies in branch-2 are very old, and some are even susce

Re: [VOTE] Move Submarine source code, documentation, etc. to a separate Apache Git repo

+1 given the scope of the future of Submarine, I think that makes sense. I am also happy to see Hadoop contributors being able to commit to Submarine repo. I think that'll help grow the Submarine community in the long run. On Mon, Aug 26, 2019 at 9:26 AM Ayush Saxena wrote: > +1 > > -Ayush > > O

[DISCUSS] GitHub PRs without JIRA number

Hi, There are hundreds of GitHub PRs pending review. Many of them just sit there wasting Jenkins resources. I suggest: (1) close PRs that went stale (i.e. doesn't compile). Or even close PRs that hasn't been reviewed for more than a year. (1) close PRs that doesn't have a JIRA number. No one is go

Re: [DISCUSS] GitHub PRs without JIRA number

atic Jenkins trigger. > I've seen the "retest this" and others: > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin > https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md > > > > On Tue, Aug 27, 2019 at 10:47 AM Wei-Chiu Chuan

Re: [DISCUSS] GitHub PRs without JIRA number

+general@ On Wed, Aug 28, 2019 at 6:42 AM Wei-Chiu Chuang wrote: > I don't think our GitHub integration supports those commands. Ozone has > its own github integration that can test individual PRs though. > > > > On Tue, Aug 27, 2019 at 12:40 PM Iñigo Goiri wrote: &g

Re: [VOTE] Moving Submarine to a separate Apache project proposal

+1 I've involved myself in Submarine dev and I'd like to be included in the future. Thanks On Sat, Sep 7, 2019 at 5:27 AM Owen O'Malley wrote: > Since you don't have any Apache Members, I'll join to provide Apache > oversight. > > .. Owen > > On Fri, Sep 6, 2019 at 1:38 PM Owen O'Malley > wrot

Re: [DISCUSS] GitHub PRs without JIRA number

Thanks for doing this! It also looks like "Scan Now" also triggers builds for non-committer's PRs. That's great! On Tue, Sep 10, 2019 at 10:21 PM 张铎(Duo Zhang) wrote: > Actually the job for testing PR is here... > > https://builds.apache.org/job/hadoop-multibranch/ > > I've added the 'Change req

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

Hi I am late to this but I am keen to understand more. To be exact, how can we better use the thirdparty repo? Looking at HBase as an example, it looks like everything that are known to break a lot after an update get shaded into the hbase-thirdparty artifact: guava, netty, ... etc. Is it the purp

How should we do about dependency update?

Hi Hadoop developers, I've always had this question and I don't know the answer. For the last few months I finally spent time to deal with the vulnerability reports from our internal dependency check tools. Say in HADOOP-16152 we update Jetty

Re: How should we do about dependency update?

dependencies where practical. I don't know how often a CVE > comes along for things like our logging API dependency, for example. > But downstream folks should definitely not rely on dependencies we use > for internal service, so I'm surprised that a version change for Jetty >

[DISCUSS] Enable github security notifications to all Hadoop committers

Hi, I raised INFRA-19327 to enable github security notification. How do people feel if we enable this notification to all committers? I already have hundreds of incoming emails from various Hadoop alias each day so I don't mind adding a few more.

Re: [DISCUSS] Enable github security notifications to all Hadoop committers

t; from various Hadoop alias each day so I don't mind adding a few more. >> >> Completely agreed. >> >> -Akira >> >> On Thu, Oct 24, 2019 at 3:48 PM Bharat Viswanadham >> wrote: >> >> > +1 (binding). I am interested in receiving th

Re: [DISCUSS] Hadoop 2019 Release Planning

I'm curious about the fate of branch-2.8 and branch-2.9. 2.9.2 is over a year old (released on 11/19/2018) 2.8.5 is over a year old too (released on 9/10/2018) It appears to me most of the development in 2.x is focusing on stabilizing 2.10 and I wonder if there are people still on 2.8/2.9. Downs

Re: Hadoop 3.1.4 Release Plan Proposal

Sounds good to me. Thanks for doing this! On Mon, Jan 20, 2020 at 4:04 AM Gabor Bota wrote: > Hi All, > > Based on the discussion on the topic "Hadoop 2019 Release Planning" I > volunteer to do the next 3.1 Hadoop release, version 3.1.4. > > You can find the blocker/critical issues and all issue

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

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 for a feature branch (1) it turns out we need to update NameNode layout version (2) It's a med

[INFO] New branch created: HDFS-14978_ec_conversion (Re: [DISCUSS] Feature branch for HDFS-14978 In-place Erasure Coding Conversion)

Thank you. FYI, I went ahead and created the branch HDFS-14978_ec_conversion On Fri, Jan 24, 2020 at 5:07 AM Ayush Saxena wrote: > +1 for the feature branch > > -Ayush > > > On 24-Jan-2020, at 3:04 AM, Wei-Chiu Chuang > wrote: > > > > Hi we are working on a

[DISCUSS] EOL Hadoop branch-2.8

The last Hadoop 2.8.x release, 2.8.5, was GA on September 15th 2018. It's been 17 months since the release and the community by and large have moved up to 2.9/2.10/3.x. With Hadoop 3.3.0 over the horizon, is it time to start the EOL discussion and reduce the number of active branches?

Re: [DISCUSS] hadoop-thirdparty 1.0.0 release

+1 On Fri, Feb 21, 2020 at 1:22 AM Akira Ajisaka wrote: > Thanks Vinayakumar for starting the discussion, > > +1 for the release plan. > I think the release vote timeframe is now 5 days, not 7 days. > > -Akira > > On Fri, Feb 21, 2020 at 3:56 PM Vinayakumar B > wrote: > > > Hi All, > > > > Sinc

Re: [DISCUSS] EOL Hadoop branch-2.8

4:59 PM Ayush Saxena wrote: > > > > > Thanx Wei-Chiu for initiating this > > > +1 for marking 2.8 EOL > > > > > > -Ayush > > > > > > > On 17-Feb-2020, at 11:14 PM, Wei-Chiu Chuang > > wrote: > > > > > > > &g

Re: [DISCUSS] EOL Hadoop branch-2.8

b 18, 2020 at 10:48 PM Akira Ajisaka > > > wrote: > > > > > > > Thanks Wei-Chiu for starting the discussion, > > > > > > > > +1 for the EoL. > > > > > > > > -Akira > > > > > > > > On Tue, Feb 18, 2020 a

[ANNOUNCE] Creation of user-zh mailing list

che.org. Non-subscribers may also post messages after the moderators' approvals. - Wei-Chiu Chuang (on behalf of the Apache Hadoop PMC)

[通知] 建立 user-zh 郵件列表

修改仍應以英文在 *-dev@, JIRAs and GitHub上進行。 這個郵件列表目前已經可以使用了，我們的網站也將再更新後加入此郵件列表。任何人都可藉由發信至 user-zh-subscr...@hadoop.apache.org 訂閱此列表。非訂閱者的信件經審核後可發出。 - 莊偉赳（Apache Hadoop PMC代表） On Fri, Feb 28, 2020 at 9:30 AM Wei-Chiu Chuang wrote: > Hi! > > Apache Hadoop welcomes contributors from around the

[VOTE] EOL Hadoop branch-2.8

ude on March 9th (Mon) 11am PST. Please feel free to share your thoughts. Thanks, Weichiu On Mon, Feb 24, 2020 at 10:28 AM Wei-Chiu Chuang wrote: > Looking at the EOL policy wiki: > https://cwiki.apache.org/confluence/display/HADOOP/EOL+%28End-of-life%29+Release+Branches > > The Hado

[DISCUSS] fate of branch-2.9

Hi, Following the discussion to end branch-2.8, I want to start a discussion around what's next with branch-2.9. I am hesitant to use the word "end of life" but consider these facts: * 2.9.0 was released Dec 17, 2017. * 2.9.2, the last 2.9.x release, went out Nov 19 2018, which is more than 15 mo

[ANNOUNCE] New Apache Hadoop Committer - Stephen O'Donnell

In bcc: general@ It's my pleasure to announce that Stephen O'Donnell has been elected as committer on the Apache Hadoop project recognizing his continued contributions to the project. Please join me in congratulating him. Hearty Congratulations & Welcome aboard Stephen! Wei-C

Re: [DISCUSS] fate of branch-2.9

> On Mon, Mar 2, 2020 at 5:12 PM, Wei-Chiu Chuang > wrote: Hi, > > Following the discussion to end branch-2.8, I want to start a discussion > around what's next with branch-2.9. I am hesitant to use the word "end of > life" but consider these facts: > > * 2.

[DISCUSS] Accelerate Hadoop dependency updates

Hi Hadoop devs, I the past, Hadoop tends to be pretty far behind the latest versions of dependencies. Part of that is due to the fear of the breaking changes brought in by the dependency updates. However, things have changed dramatically over the past few years. With more focus on security vulner

Re: [VOTE] EOL Hadoop branch-2.8

This is to conclude the vote result. with 10 +1 binding votes and 0 -1 votes. This vote is passed. I'll proceed with a formal announcement. On Mon, Mar 9, 2020 at 2:22 AM Sammi Chen wrote: > +1. > Thanks, Wei-Chiu. > > BR, > Sammi > > On Tue, Mar 3, 2020 at 2:48

[ANNOUNCEMENT] Apache Hadoop 2.8.x release line end of life

newer release lines: 2.10.0 / 3.1.3 / 3.2.1. Please check out our Release EOL wiki for details: https://cwiki.apache.org/confluence/display/HADOOP/EOL+(End-of-life)+Release+Branches Best Regards, Wei-Chiu Chuang (On Behalf of the Apache Hadoop PMC)

Re: [DISCUSS] Accelerate Hadoop dependency updates

;s guava is in the classpath of every application. Thoughts? On Sat, Mar 7, 2020 at 9:31 AM Wei-Chiu Chuang wrote: > Hi Hadoop devs, > > I the past, Hadoop tends to be pretty far behind the latest versions of > dependencies. Part of that is due to the fear of the breaking changes > bro

[NOTICE] branch HADOOP-15566-OpenTracing created

Hi devs, I forked a branch HADOOP-15566-OpenTracing from trunk. This branch is used to develop HADOOP-15566 (OpenTracing support in Hadoop)

Re: [DISCUSS] Accelerate Hadoop dependency updates

t; appropriate for Hadoop 3.3.0 release than 3.2.1. > > On Tue, Mar 10, 2020 at 3:03 PM Wei-Chiu Chuang > wrote: > >> I'm not hearing any feedback so far, but I want to suggest: >> >> use hadoop-thirdparty repository to host any dependencies that are known >&

Re: [DISCUSS] Accelerate Hadoop dependency updates

nor > CDH release? Or this is in preparation for the next major/minor release of > CDH? > > On Wed, Mar 11, 2020 at 5:45 PM Wei-Chiu Chuang > wrote: > >> FWIW we are updating guava in Spark and Hive at Cloudera. Don't know which >> Apache version are they going to land,

2.10.1 release?

The 2.10.0 release went GA roughly 5 months ago. A bunch of issues were fixed. If any one's interested in being the Release Manager, I've made your work slightly easier: Here's a dashboard for 2.10.1 issues. I granted edit permission to all committers. https://issues.apache.org/jira/secure/Dashbo

[DISCUSS] Shade guava into hadoop-thirdparty

Hi Hadoop devs, I spent a good part of the past 7 months working with a dozen of colleagues to update the guava version in Cloudera's software (that includes Hadoop, HBase, Spark, Hive, Cloudera Manager ... more than 20+ projects) After 7 months, I finally came to a conclusion: Update to Hadoop 3

Re: [DISCUSS] Shade guava into hadoop-thirdparty

s that will require recompiling all client > applications because they need to use shaded Guava classes? > > On Sat, Apr 4, 2020 at 12:13 PM Wei-Chiu Chuang > wrote: > >> Hi Hadoop devs, >> >> I spent a good part of the past 7 months working with a dozen of >> colle

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

t;> Thanks and regards, >>> Akira >>> >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula >>> wrote: >>> >>>> Hi All, >>>> >>>> we are down to two blockers issues now (YARN-10194 and YARN-9848) which >>

Re: Hadoop 3.1.4 Release Code Freeze

Gabor, can you also create the dot release branch so folks can start cherrypicking commits for 3.1.5? Thank you On Wed, Apr 22, 2020 at 3:54 AM Gabor Bota wrote: > Hi All, > > The code freeze for Hadoop 3.1.4 release is planned for today. There > some issues still open for that version. > > Thes

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

Gabor, I'm sorry there's a test failure in branch-3.1 HDFS-14599 1. 1. I just cherrypicked the fix to branch-3.2 branch-3.1. It's a test only fix so technically I could live with it. But it would be best to add the fix to 3.1.

Re: [DISCUSS] making Ozone a separate Apache project

+1 On Wed, May 13, 2020 at 8:32 AM anu engineer wrote: > +1 > —Anu > > > On May 13, 2020, at 12:53 AM, Elek, Marton wrote: > > > >  > > > > I would like to start a discussion to make a separate Apache project for > Ozone > > > > > > > > ### HISTORY [1] > > > > * Apache Hadoop Ozone development

[ANNOUNCE] New Apache Hadoop Committer - He Xiaoqiao

In bcc: general@ It's my pleasure to announce that He Xiaoqiao has been elected as a committer on the Apache Hadoop project recognizing his continued contributions to the project. Please join me in congratulating him. Hearty Congratulations & Welcome aboard Xiaoqiao! Wei-Chiu Chuang (

Mandarin Hadoop online sync this week

Hello, There hasn't been a Mandarin online sync for quite some time. I'd like to call for one this week: Date/time: 8/27 Thursday Beijing Time 1PM 8/26 Wednesday US Pacific Time 10PM Link: https://cloudera.zoom.us/j/880548968 Past sync summary: https://docs.google.com/document/d/1jXM5Ujvf-zhcy

Re: Mandarin Hadoop online sync this week

committers? On Tue, Aug 25, 2020 at 9:58 AM Brahma Reddy Battula wrote: > HI, > > what you are planning for this week? > > On Tue, Aug 25, 2020 at 10:18 PM Wei-Chiu Chuang > wrote: > >> Hello, >> >> There hasn't been a Mandarin online sync for quite s

Re: Mandarin Hadoop online sync this week

ed we can port Ozone features into Hadoop Common. For example, Java-based configuration is a power feature which can benefit Hadoop as well. On Tue, Aug 25, 2020 at 9:47 AM Wei-Chiu Chuang wrote: > Hello, > > There hasn't been a Mandarin online sync for quite some time. I'd lik

Re: [DISCUSS] fate of branch-2.9

hanks, Weichiu On Fri, Mar 6, 2020 at 5:47 PM Wei-Chiu Chuang wrote: > I think that's a great suggestion. > Currently, we make 1 minor release per year, and within each minor release > we bring up 1 thousand to 2 thousand commits in it compared with the > previous one. > I can t

[DISCUSS] Hadoop 2.10.1 release

Hello, I see that Masatake graciously agreed to volunteer with the Hadoop 2.10.1 release work in the 2.9 branch EOL discussion thread https://s.apache.org/hadoop2.9eold Anyone else likes to contribute also? Thanks

[DISCUSS] Hadoop 3.2.2 release

Hi folks, I was reminded by Xiaoqiao that Hadoop 3.2.1 was made almost a year ago (released on September 22, 2019) and we're overdue for a follow-up. @Rohith Sharma K S you were the RM for Hadoop 3.2.1. Are we planning to make the 3.2.2 releases soon? Xiaoqiao wants to help with the release. T

[ANNOUNCEMENT] Apache Hadoop 2.9.x release line end of life

newer release lines: 2.10.0 / 3.1.4 / 3.2.1 / 3.3.0. Please check out our Release EOL wiki for details: https://cwiki.apache.org/confluence/display/HADOOP/EOL+(End-of-life)+Release+Branches Best Regards, Wei-Chiu Chuang (On Behalf of the Apache Hadoop PMC)

Re: Sep. Y2020 Hadoop Meetup in China

This is great news! Can you also share this with the user@ and user-zh@ mailing lists? We need to get the message out. On Tue, Sep 15, 2020 at 10:36 PM 俊平堵 wrote: > Hi, > Last year Aug, we had a very successful meetup in Beijing ( > https://blogs.apache.org/hadoop) which help to promote hado

Two more binding votes required for Apache Hadoop 2.10.1 RC0

Masatake is doing a great job rolling out 2.10.1 RC0. Let's give him a final push to get it out. Thanks, Wei-Chiu

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

+1 (binding) I did a security scan for the 2.10.1 RC0 and it looks fine to me. Checked recent critical/blocker HDFS issues that are not in 2.10.1. It looks mostly fine. Most of them are Hadoop 3.x features (EC, ... etc) but there is one worth attention: 1. HDFS-14674

[ANNOUNCE] Lisheng Sun is a new Apache Hadoop Committer

ssues.apache.org/jira/browse/HDFS-13694> and HDFS-13693 <https://issues.apache.org/jira/browse/HDFS-13693>. Code wise, he resolved 57 Hadoop jiras. Let's congratulate Lisheng for this new role! Cheers, Wei-Chiu Chuang (on behalf of the Apache Hadoop PMC)

[ANNOUNCE] Hui Fei is a new Apache Hadoop Committer

y Sync Online > > https://docs.google.com/document/d/1jXM5Ujvf-zhcyw_5kiQVx6g-HeKe-YGnFS_1-qFXomI/edit#heading=h.irqxw1iy16zo > where >he discussed the Hadoop 3 rolling upgrade support > > Let's congratulate Hui for this new role! Cheers, Wei-Chiu Chuang (on behalf of the Apache Hadoop PMC)

Re: [VOTE] Moving Ozone to a separated Apache project

+1 Look forward to it. On Tue, Sep 29, 2020 at 4:48 PM Konstantin Shvachko wrote: > +1 > > Stay safe, > --Konstantin > > On Thu, Sep 24, 2020 at 10:59 PM Elek, Marton wrote: > > > Hi all, > > > > Thank you for all the feedback and requests, > > > > As we discussed in the previous thread(s) [1]

Re: Hadoop 3.2.2 Release Code Freeze Plan

Thanks Xiaoqiao! Glad to see this is moving along. I noticed your dashboard has private filters and therefore the results are not visible publicly. On Tue, Sep 29, 2020 at 10:02 PM Xiaoqiao He wrote: > Hi All, > > Plan to code frozen for Hadoop-3.2.2 release at 2020/10/15. From now on, > most of

JIRA privilege for committers/PMCs

Hi, Is there any one who is a Hadoop committer or PMC, but who does not have the committer/administrator privilege (e.g. assign/resolve jiras)? JIRA projects like HADOOP has "hadoop" and "hadoop-pmc" groups added as administrators. [image: Screen Shot 2020-10-14 at 3.20.59 PM.png] So I would hav

Re: Fixing flaky tests in Apache Hadoop

Thanks for raising the issue, Akira and Ahmed, Fixing flaky tests is a thankless job so I want to take this opportunity to recognize the time and effort. We will always have flaky tests due to bad tests or simply infra issues. Fixing flaky tests will take time but if they are not addressed it was

Re: Fixing flaky tests in Apache Hadoop

at 2:03 PM Wei-Chiu Chuang wrote: > Thanks for raising the issue, Akira and Ahmed, > > Fixing flaky tests is a thankless job so I want to take this opportunity > to recognize the time and effort. > > We will always have flaky tests due to bad tests or simply infra issues. > Fi

Fwd: Heads-up, Apache Yetus looking for feedback on RC with lots of changes

Forwarding to the Hadoop devs -- Forwarded message - From: Sean Busbey Date: Tue, Nov 3, 2020 at 9:51 AM Subject: Heads-up, Apache Yetus looking for feedback on RC with lots of changes To: dev Hi folks! FYI, Apache Yetus is doing RCs for their 0.13.0 release and it's got a lot

Committers please subscribe to security@hadoop

The security@hadoop mailing list is restricted to Hadoop committers. Subscribing to the mailing list is not an automatic process. If you are a committer, please subscribe by sending an email to security-subscr...@hadoop.apache.org so we can discuss vulnerabilities in private. Thanks, Wei-Chiu

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC2

I suggest we wait for HDFS-15680 (If I understand it correctly, it's a blocker) I wish to update jetty too in this release, but it's turning out to be more involved than i had anticipated. On Fri, Nov 13, 2020 at 3:22 PM Chao Sun wrote: > +1 (

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC4

Diff between RC3 and RC4: MAPREDUCE-7284. TestCombineFileInputFormat#testMissingBlocks fails (#2136) HDFS-13404. Addendum: RBF: TestRouterWebHDFSContractAppend.testRenameFileBeingAppended fail. Contributed by Takanobu Asanuma. HADOOP-16080. hadoop-aws does not work with hadoop-client-api (#2510)

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC4

Forgot to mention I am +1 (binding) too based on the fact there are no blocker issues and RC3 and RC4 diff. On Mon, Dec 14, 2020 at 1:42 PM Wei-Chiu Chuang wrote: > Diff between RC3 and RC4: > > MAPREDUCE-7284. TestCombineFileInputFormat#testMissingBlocks fails (#2136) > HDFS-134

Re: [E] Re: [VOTE] Release Apache Hadoop 3.2.2 - RC4

We should target 3.4.0, 3.3.1 3.2.3 (or 3.2.2) I updated and set 3.3.0 released in YARN. Time to clean up some of the old releases. I'll do that. On Mon, Dec 21, 2020 at 4:04 PM Eric Badger wrote: > I've committed https://issues.apache.org/jira/browse/YARN-10540. Xiaoqiao, > feel free to cherr

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC5

+1 (binding) On Mon, Jan 4, 2021 at 11:11 PM Akira Ajisaka wrote: > +1 (binding) > > - Verified the checksums and signatures > - Verified the source is the same as the RC5 tag > - Built from source with CentOS 7.9 and Java 1.8.0_275 > - Setup pseudo cluster and ran some FsShell commands > > Than

[DISCUSS] Hadoop 3.3.1 release

Hi all, Hadoop 3.3.0 was released half a year ago, and as of now we've accumulated more than 400 changes in the branch-3.3. A number of downstreamers are eagerly waiting for 3.3.1 which addresses the guava version conflict issue. https://issues.apache.org/jira/issues/?filter=-1&jql=project%20in%2

Re: [DISCUSS] Hadoop 3.3.1 release

ks > > >> >> > Sunil > > >> >> > > > >> >> > On Mon, Feb 8, 2021 at 11:56 PM Stack wrote: > > >> >> > > > >> >> > > On Wed, Feb 3, 2021 at 6:41 AM Steve Loughran > > >> >>

Re: [DISCUSS] Hadoop 3.3.1 release

te reply.. > > > > > >> >> > > > > > >> >> I will come up with a plan.. Please let me know if anybody > has > > > some > > > > > >> >> features/improvements/bugs that need to be included. >

Re: [DISCUSS] Hadoop 3.3.1 release

the release, please tag the jira with the label 'release-blocker'. On Tue, Apr 20, 2021 at 2:44 AM Billie Rinaldi wrote: > I was thinking of backporting HADOOP-16948 for 3.3.1. > > Billie > > On Mon, Apr 19, 2021 at 1:33 AM Wei-Chiu Chuang > wrote: > > > H

[DISCUSS] hadoop-thirdparty 1.1.0 release

Hi community, In preparation of the Hadoop 3.3.1 release, I am starting a thread to discuss its prerequisite: the release of hadoop-thirdparty 1.1.0. My plan: update guava to 30.1.1 (latest). I have the PR ready to merge. Do we want to update protobuf and jaeger? Anything else? I suppose we won

Re: [DISCUSS] hadoop-thirdparty 1.1.0 release

version anyway. The version used is too old. On Fri, Apr 23, 2021 at 10:55 AM Wei-Chiu Chuang wrote: > Hi community, > > In preparation of the Hadoop 3.3.1 release, I am starting a thread to > discuss its prerequisite: the release of hadoop-thirdparty 1.1.0. > > My plan: >

  1   2   >