[jira] [Created] (MAPREDUCE-6655) Fix a typo (STRICT_IE6) in Encrypted Shuffle

2016-03-19 Thread Wei-Chiu Chuang (JIRA)
Wei-Chiu Chuang created MAPREDUCE-6655: -- Summary: Fix a typo (STRICT_IE6) in Encrypted Shuffle Key: MAPREDUCE-6655 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6655 Project: Hadoop Map

Re: [VOTE] Release Apache Hadoop 2.7.3 RC0

2016-07-26 Thread Wei-Chiu Chuang
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

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

2016-10-25 Thread Wei-Chiu Chuang
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

Re: HADOOP-14316: Switching from Findbugs to Spotbugs

2017-04-19 Thread Wei-Chiu Chuang
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 <a...@effectivemachines.com> > wrote: >

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

2017-03-21 Thread Wei-Chiu Chuang
-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 <aajis...@apache.org> wrote: > > Thanks J

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

2017-08-04 Thread Wei-Chiu Chuang
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: [VOTE] Release Apache Hadoop 3.0.0 RC1

2017-12-12 Thread Wei-Chiu Chuang
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

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

2017-12-13 Thread Wei-Chiu Chuang
from the create-release process, > 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 <weic...@cloudera.com> >

Re: [DISCUSS] Apache Hadoop 2.7.5 Release Plan

2017-11-17 Thread Wei-Chiu Chuang
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

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

2017-11-20 Thread Wei-Chiu Chuang
@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

Re: Apache Hadoop 3.0.3 Release plan

2018-05-08 Thread Wei-Chiu Chuang
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: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

2018-07-05 Thread Wei-Chiu Chuang
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

Re: Apache Hadoop 2.9.1 Release Plan

2018-04-06 Thread Wei-Chiu Chuang
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 <weic...@cloudera.com> wrote: > >1. > Looks like: >2. HDFS-13347 <https://issues.apache.org/j

Re: Apache Hadoop 2.9.1 Release Plan

2018-04-04 Thread Wei-Chiu Chuang
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

Re: Apache Hadoop 2.9.1 Release Plan

2018-04-06 Thread Wei-Chiu Chuang
.1 release. > > Would 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 <sammi.c...@int

Re: Hadoop 3.2 Release Plan proposal

2018-10-19 Thread Wei-Chiu Chuang
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

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

2019-04-03 Thread Wei-Chiu Chuang
+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,

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

2019-06-18 Thread Wei-Chiu Chuang
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: > >

HDFS-13287 broke the build; reverted

2019-06-19 Thread Wei-Chiu Chuang
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!

Revert of HDFS-12914 breaks the branch-2

2019-08-12 Thread Wei-Chiu Chuang
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

Re: Unassigned Hadoop jiras with patch available

2019-08-15 Thread Wei-Chiu Chuang
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. > > Ho

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

2019-07-24 Thread Wei-Chiu Chuang
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

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

2019-07-25 Thread Wei-Chiu Chuang
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 Sep 15 >

[DISCUSS] Prefer Github PR Integration over patch in JIRA

2019-07-22 Thread Wei-Chiu Chuang
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

Unassigned Hadoop jiras with patch available

2019-07-31 Thread Wei-Chiu Chuang
I am using this jira filter to find jiras with patch available but unassigned.

Re: Unassigned Hadoop jiras with patch available

2019-07-31 Thread Wei-Chiu Chuang
%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=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2CSUBM

Re: Unassigned Hadoop jiras with patch available

2019-08-01 Thread Wei-Chiu Chuang
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

2019-08-08 Thread Wei-Chiu Chuang
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

Re: Make EOL branches to public?

2019-08-20 Thread Wei-Chiu Chuang
+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

Re: [DISCUSS] Hadoop-3.2.1 release proposal

2019-08-20 Thread Wei-Chiu Chuang
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: [VOTE] Move Submarine source code, documentation, etc. to a separate Apache Git repo

2019-08-26 Thread Wei-Chiu Chuang
+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 > >

Re: [DISCUSS] GitHub PRs without JIRA number

2019-08-28 Thread Wei-Chiu Chuang
enkins 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 Chuang > wrote:

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

2019-08-26 Thread Wei-Chiu Chuang
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

[DISCUSS] GitHub PRs without JIRA number

2019-08-27 Thread Wei-Chiu Chuang
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

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-04 Thread Wei-Chiu Chuang
+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

2019-09-06 Thread Wei-Chiu Chuang
+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 >

Re: [DISCUSS] GitHub PRs without JIRA number

2019-09-11 Thread Wei-Chiu Chuang
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