Apache Hadoop 2.9.2 release plan

/critical bugs targeted for 2.9.2 now [2], so I plan to cut branch-2.9.2 and create RC by the end of this week. If someone want to be a release manager for 2.9.2. You can do it instead of me, and I'll help you. Please feel free to share your thoughts. Thanks, Akira Ajisaka [1] https

Re: Apache Hadoop 2.9.2 release plan

branch-2.9.2 is cut and moved the 2.9.2-targeted jiras to 2.9.3. Hi committers, please set the fix version to 2.9.3 when you commit a fix in branch-2.9. Thanks, Akira 2018年11月1日(木) 13:52 Akira Ajisaka : > > I have been checking the blocker/critical issues fixed in branch-2 and > not in b

Re: Apache Hadoop 2.9.2 release plan

] to 2.9.3. -Akira [1] https://s.apache.org/2.9-candidate-jiras [2] https://s.apache.org/2.9.2-targeted-jiras 2018年10月29日(月) 17:28 Akira Ajisaka : > > Hi all, > > We have released Apache Hadoop 2.9.1 on May 5, 2018. To further > improve the quality of the release, I'm planning t

Re: branch-2.9.2 is almost closed for commit

Recently I hit the gpg-agent cache ttl issue while creating 2.9.2 RC0, and the issue was fixed by HADOOP-15923. I'll create RC0 and start the vote by the end of this week. Sorry for the delay. Thanks, Akira 2018年11月6日(火) 13:51 Akira Ajisaka : > > Hi folks, > > Now there is only 1 cri

Re: branch-2.9.2 is almost closed for commit

. -Akira 2018年11月13日(火) 16:07 Akira Ajisaka : > > Recently I hit the gpg-agent cache ttl issue while creating 2.9.2 RC0, > and the issue was fixed by HADOOP-15923. > I'll create RC0 and start the vote by the end of this week. Sorry for the > delay. > > Thanks, > Akira > 2018年1

[VOTE] Release Apache Hadoop 2.9.2 (RC0)

Hi folks, I have put together a release candidate (RC0) for Hadoop 2.9.2. It includes 204 bug fixes and improvements since 2.9.1. [1] The RC is available at http://home.apache.org/~aajisaka/hadoop-2.9.2-RC0/ Git signed tag is release-2.9.2-RC0 and the checksum is

branch-2.9.2 is almost closed for commit

Hi folks, Now there is only 1 critical issues targeted for 2.9.2 (YARN-8233), so I'd like to close branch-2.9.2 except YARN-8233. I create RC0 as soon as YARN-8233 is committed to branch-2.9.2. Thanks, Akira - To unsubscribe,

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

eline) >- verified some operations of Router-based Federation > > Thanks, > -Takanobu > > on 2018/11/14 10:02, "Akira Ajisaka" wrote: > > Hi folks, > > I have put together a release candidate (RC0) for Hadoop 2.9.2. It > includes 204 bug fixes

Re: HDFS/HDDS unit tests running failed in Jenkins precommit building

+ common-dev, mapreduce-dev, yarn-dev Probably this issue is caused by https://issues.apache.org/jira/browse/SUREFIRE-1588 and fixed by Maven surefire plugin 3.0.0-M1. I filed a JIRA and uploaded a patch to upgrade the version of the plugin. Please check

Re: [DISCUSS] Move to gitbox

enkins jobs? Regards, Akira 2018年12月12日(水) 15:33 Ajay Kumar : > > +1 (non-binding) > > On 12/11/18, 9:07 PM, "Brahma Reddy Battula" wrote: > > +1 > > > > On Sat, Dec 8, 2018 at 1:26 PM, Akira Ajisaka wrote: > > > Hi all, > >

Re: [DISCUSS] Move to gitbox

7:57 AM, Elek, Marton wrote: > > > > > > > > On 12/12/18 12:27 PM, Akira Ajisaka wrote: > >> Thank you for your positive feedback! I'll file a jira to INFRA in this > >> weekend. > >> > >>> If I understood well the only bigger t

[NOTICE] Move to gitbox

Hi all, The Apache Hadoop git repository will be migrated to gitbox at 9PM UTC in 30th December. After the migration, the old repository cannot be accessed. Please use the new repository for committing. The migration is pretty much atomic and it will take up to a few minutes. Old repository:

Re: [DISCUSS] Move to gitbox

Thank you Daniel for your answer! -Akira 2018年12月14日(金) 18:36 Daniel Gruno : > > On 12/14/18 6:50 AM, Akira Ajisaka wrote: > > Hi ASF infrastructure team, > > > > Could you answer the following questions? > > > > * Is it an atomic move? Or will both repos li

Re: [VOTE] Release Apache Hadoop 3.2.0 - RC0

Thanks Sunil for driving this release. +1 (binding) - verified signatures and checksums - checked the documents including changes and release notes - built from source on CentOS 7.5, Java 1.8.0_191 - ran some MapReduce jobs in pseudo-distributed cluster - checked some web UIs (NN, DN, RM, NM)

[DISCUSS] Move to gitbox

Hi all, Apache Hadoop git repository is in git-wip-us server and it will be decommissioned. If there are no objection, I'll file a JIRA ticket with INFRA to migrate to https://gitbox.apache.org/ and update documentation. According to ASF infra team, the timeframe is as follows: > - December 9th

[ANNOUNCE] Apache Hadoop 2.9.2 release

Hi all, I am pleased to announce that the Apache Hadoop 2.9.2 has been released. Apache Hadoop 2.9.2 is the next release of Apache Hadoop 2.9 line, which includes 204 fixes since previous Hadoop 2.9.1 release. - For major changes included in Hadoop 2.9 line, please refer Hadoop 2.9.2 main page

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

Payne > > > > > > > > > > > > On Tuesday, November 13, 2018, 7:02:51 PM CST, Akira Ajisaka < > > aajis...@apache.org> wrote: > > > > Hi folks, > > > > I have put together a release candidate (RC0) for Hadoop 2.9.2. It > > incl

Re: HDFS/HDDS unit tests running failed in Jenkins precommit building

kins > like this one > (https://builds.apache.org/job/PreCommit-HDDS-Build/1801/artifact/out/patch-unit-hadoop-ozone_common.txt). > Can you help take a look? > > Thanks, > Xiaoyu > > > On 11/9/18, 1:29 AM, "Akira Ajisaka" wrote: > > + common-de

Re: [NOTICE] Move to gitbox

Hi all, The migration has been finished. All the jenkins jobs under the hadoop view and ozone view were also updated except the beam_PerformanceTests_* jobs. Thank you Elek and ASF infra team for your help! Regards, Akira 2018年12月25日(火) 13:27 Akira Ajisaka : > > Hi all, > > The A

Re: [NOTICE] Move to gitbox

pdated with > > the new location. > > > > It is still pointing to https://git-wip-us.apache.org/repos/asf/hadoop.git > > > > Checking out the source still has its mention > > As > > git clone git://git.apache.org/hadoop.git > > > > Or this link needs

[DISCUSS] Use of AssertJ for testing

Hi folks, Now I'm going to upgrade the JUnit version from 4 to 5 for Java 11 support. I wanted to start with the small module, so I uploaded a patch to upgrade the API in hadoop-yarn-api module at first (YARN-8943), and in this JIRA, Szilard Nemeth suggested using AssertJ with JUnit 5. (Thanks

Re: Github and GitBox are inconsistent

This issue was fixed by ASF infra team. If there are any problems, please let me know. Regards, Akira On Mon, Mar 4, 2019 at 3:25 PM Akira Ajisaka wrote: > > Hi folks, > > I found github and gitbox are inconsistent and filed > https://issues.apache.org/jira/browse/INF

Github and GitBox are inconsistent

Hi folks, I found github and gitbox are inconsistent and filed https://issues.apache.org/jira/browse/INFRA-17947 to fix it. Regards, Akira - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional

Re: Proposal: Force 'squash and merge' on github UI

perience of the spark > > process, which has > > > > * A template for the PR text which is automatically used to initialize the > > text > > * strict use of reviewers demanding everything right (no > > committer-final-cleanup) > > * the ability of tr

Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+

lopers? > It would be better to make it confident that old hamlet of Hadoop 3 is > used nowhere. > > I'm +1 on making imcompatible change if this blocks another Java > migration issues, > while I don't see strong reason to hurry as I see the patch of YARN-9279. > > Masatake

Re: Including Original Author in git commits.

Hi Vinay, I'm already doing this if I can get the original author name and the email address in some way. If the patch is created by git format-patch command, smart-apply-patch --committer option can do this automatically. Thanks, Akira On Thu, Feb 14, 2019 at 3:27 PM Vinayakumar B wrote: > >

Re: [VOTE] Moving branch-2 precommit/nightly test builds to java 8

+1 -Akira On Wed, Feb 6, 2019 at 9:13 AM Wangda Tan wrote: > > +1, make sense to me. > > On Tue, Feb 5, 2019 at 3:29 PM Konstantin Shvachko > wrote: > > > +1 Makes sense to me. > > > > Thanks, > > --Konst > > > > On Mon, Feb 4, 2019 at 6:14 PM Jonathan Hung wrote: > > > > > Hello, > > > > > >

Re: [DISCUSS] Use of AssertJ for testing

for getting this done. > --Anu > > > On 3/31/19, 9:37 PM, "Akira Ajisaka" wrote: > > Hi folks, > > Now I'm going to upgrade the JUnit version from 4 to 5 for Java 11 > support. > I wanted to start with the small module, so I uploaded a patch to upgr

Re: Incorrect NOTICE files in TLP releases

Hi Vinod, This issue is now tracked by https://issues.apache.org/jira/browse/HADOOP-15958 Thanks, Akira On Fri, Jul 5, 2019 at 1:29 PM Vinod Kumar Vavilapalli wrote: > > A bit of an old email, but want to make sure this isn't missed. > > Has anyone looked into this concern? > > Ref

Re: [DISCUSS] Prefer JUnit5 for new tests

collections; > very verbose for classic assertTrue/assertFalse, but can be used to generate > great error strings > > On Fri, Jul 26, 2019 at 9:26 AM Akira Ajisaka wrote: >> >> Hi folks, >> >> Now we are slowly migrating from JUnit4 to JUnit5. >> https://issue

Re: [DISCUSS] Hadoop 2019 Release Planning

Thanks all for the discussion, - I'd like the volunteered release managers to review this issue: https://issues.apache.org/jira/browse/HADOOP-16494 - I can co-RM for a release. Thanks and regards, Akira On Fri, Aug 16, 2019 at 6:49 PM Wangda Tan wrote: > > Thanks all for the suggestions and

Re: Make EOL branches to public?

+1 Thank you for the discussion. -Akira On Wed, Aug 21, 2019 at 5:51 AM Wei-Chiu Chuang wrote: > > +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, > > >

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

+1 Thanks, Akira On Sat, Aug 24, 2019 at 11:06 AM Wangda Tan wrote: > > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of >

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

+1 -Akira On Wed, Aug 21, 2019 at 12:10 PM Jonathan Hung wrote: > > +1. Thanks! > > Jonathan Hung > > > On Tue, Aug 20, 2019 at 8:03 PM Wangda Tan wrote: > > > Hi all, > > > > This is a vote thread to mark any versions smaller than 2.7 (inclusive), > > and 3.0 EOL. This is based on discussions

Re: [DISCUSS] GitHub PRs without JIRA number

Thanks all for the discussion. I'm +1 for adding PR template and I wrote a patch long ago: https://issues.apache.org/jira/browse/HADOOP-15184 I'm interested in "test this", "retest this", etc. I'll file a jira for this feature. -Akira On Thu, Sep 5, 2019 at 4:05 AM Sean Busbey wrote: > We

Re: [VOTE] Force "squash and merge" option for PR merge on github UI

Makes sense, +1 On Thu, Jul 18, 2019 at 10:01 AM Sangjin Lee wrote: > > +1. Sounds good to me. > > On Wed, Jul 17, 2019 at 10:20 AM Iñigo Goiri wrote: > > > +1 > > > > On Wed, Jul 17, 2019 at 4:17 AM Steve Loughran > > > > wrote: > > > > > +1 for squash and merge, with whoever does the merge

[DISCUSS] Prefer JUnit5 for new tests

Hi folks, Now we are slowly migrating from JUnit4 to JUnit5. https://issues.apache.org/jira/browse/HADOOP-14693 However, as Steve commented [1], if we are going to migrate the existing tests, the backporting cost will become too expensive. Therefore, I'd like to recommend using JUnit5 for new

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

I'm +1 for 1 more release in 2.8.x and declare that 2.8 is EoL. > would be even happier if we could move people to 2.9.x Agreed. -Akira On Thu, Jul 25, 2019 at 10:59 PM Steve Loughran wrote: > > I'm in favour of 1 more release (it fixes the off-by 1 bug in > S3AInputStream HADOOP-16109), but

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

Thanks Wei-Chiu for starting the discussion, +1 > I already have hundreds of incoming emails 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

Re: [DISCUSS] Making 2.10 the last minor 2.x release

Thank you for your work, Jonathan. I found branch-2 has been unintentionally pushed again. Would you remove it? I think the branch should be protected if possible. -Akira On Tue, Dec 10, 2019 at 5:17 AM Jonathan Hung wrote: > It's done. The new commit chain is: trunk -> branch-3.2 ->

Re: This week's Hadoop storage community call

+cc: yarn-dev/mapreduce-dev since it contains the information for Hadoop 3.3.0 release Thank you all for the discussion and thanks Wei-Chiu for the summary. > I created a dashboard to track the Hadoop 3.3.0 release: > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335311 >

Re: [VOTE] EOL Hadoop branch-2.8

gt;>> On Mon, Feb 24, 2020 at 11:47 PM Wei-Chiu Chuang > >>> wrote: > >>> > >>>> This thread has been running for 7 days and no -1. > >>>> > >>>> Don't think we've established a formal EOL process, but to publicize > the > >&

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

+1 for the feature branch. On Fri, Jan 24, 2020 at 6:34 AM 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] EOL Hadoop branch-2.8

Thanks Wei-Chiu for starting the discussion, +1 for the EoL. -Akira On Tue, Feb 18, 2020 at 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: > > > > The last Hadoop 2.8.x release,

Re: [DISCUSS] hadoop-thirdparty 1.0.0 release

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, > > Since Hadoop-3.3.0 release is around the corner, its time to release >

Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+

the precommit job ignores new javadoc warnings/errors in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove the package to make the investigation easier. Regards, Akira On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka wrote: > Thanks Masatake for your comments. > Added the

Re: [DISCUSS] Making 2.10 the last minor 2.x release

ted, > we can’t delete it directly. > > Ref: https://issues.apache.org/jira/browse/INFRA-19581 > > -Ayush > > On 23-Dec-2019, at 5:03 PM, Akira Ajisaka wrote: > > Thank you for your work, Jonathan. > > I found branch-2 has been unintentionally pushed again. Would yo

Re: [DISCUSS] Hadoop 2019 Release Planning

Thank you Wangda. Now it's 2020. Let's release Hadoop 3.3.0. I created a wiki page for tracking blocker/critical issues for 3.3.0 and I'll check the issues in the list. https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.3+Release If you find blocker/critical issues in trunk, please set

Re: [DISCUSS] Hadoop 2019 Release Planning

l.. >> >> >> >> On Mon, 6 Jan 2020 at 6:08 PM, Gabor Bota >> wrote: >> >>> I'm interested in doing a release of hadoop. >>> The version we need an RM is 3.1.3 right? What's the target date for >>> that? >>> >>> Thanks, &g

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

Hi Brahma, I think we cannot do any of your proposed actions. http://www.apache.org/legal/release-policy.html#owned-controlled-hardware > Strictly speaking, releases must be verified on hardware owned and controlled by the committer. That means hardware the committer has physical possession and

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

lease let me know. > > i) Single machine and share cred to future RM ( as we can delete keys once > release is over). > ii) Creating the jenkins project ( may be we need to discuss in the > board..) > iii) I can provide ARM release for future releases. > > > > > > &

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

+1 - Verified signatures and checksums - Built jars and docs from source - Built hadoop trunk with hadoop-thirdparty 1.0.0 - Checked rat files and documents - Checked LICENSE and NOTICE files Thanks, Akira On Thu, Mar 12, 2020 at 5:26 AM Vinayakumar B wrote: > Hi folks, > > Thanks to

Re: [DISCUSS] Making 2.10 the last minor 2.x release

/), >> and they are not very helpful at this point. >> Can we change the QBT tests to run against branch-2.10 instead? >> >> Jim >> >> On Mon, Dec 23, 2019 at 7:44 PM Akira Ajisaka >> wrote: >> >>> Thank you, Ayush. >>> >>> I un

Moving to Yetus 0.12.0

Hi folks, I updated Jenkinsfile to use Yetus 0.12.0 in GitHub PR. https://issues.apache.org/jira/browse/HADOOP-16944 In addition, I'm updating the configs in the Jenkins jobs to use Yetus 0.12.0 in ASF JIRAs. I updated the settings of

Re: Moving to Yetus 0.12.0

On Sun, Apr 19, 2020 at 3:41 AM Akira Ajisaka wrote: > Hi folks, > > I updated Jenkinsfile to use Yetus 0.12.0 in GitHub PR. > https://issues.apache.org/jira/browse/HADOOP-16944 > > In addition, I'm updating the configs in the Jenkins jobs to use Yetus > 0.12.0 in

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

ras >>> > >>> >>> Szilard >>> >>> Nemeth < >>> >>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=snemeth> >>> >>> [image: >>> >>> Minor] PATCH AVAILABLE *Unresolved* 11/Apr

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

Hi Brahma, How is this issue going? If there are some blockers, I can help you. -Akira On Mon, Mar 30, 2020 at 3:50 AM Brahma Reddy Battula wrote: > Hi All, > > branch-3.3 created[1] and trunk set to 3.4.0-SNAPSHOT. > > while committing jira's please set the proper fix version and if there

Re: [DISCUSS] Shade guava into hadoop-thirdparty

+1 Thanks, Akira On Sun, Apr 5, 2020 at 4:13 AM Wei-Chiu Chuang wrote: > 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

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

s might confuse or sombody might miss to commit.Shall I > wait till this weekend to create..? > > On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka > wrote: > >> Hi Brahma, >> >> Thank you for preparing the release. >> Could you cut branch-3.3.0? I would like

Access to Hadoop QA account for migrating Precommit jobs in Hadoop

Hi Allen, I'm testing new Jenkins master and find that we have to set hadoopqa JIRA password to migrate the PreCommit-Admin and PreCommit-(HADOOP|HDFS|YARN|MAPREDUCE)-Build. Would you migrate the jobs or register the credential to the new Jenkins master ( https://ci-hadoop.apache.org/)? Best

Re: Moving to Yetus 0.12.0

, Apr 19, 2020 at 5:05 PM Akira Ajisaka wrote: > Updated Precommit-(HADOOP|HDFS|YARN|MAPREDUCE)-Build jobs. The daily qbt > jobs are kept as-is. Now I'm testing the new CI servers and testing the qbt > jobs with Yetus 0.12.0. > https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java

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

287 ( Open: Under > > discussion > > > ) > > > https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available) > > > https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available) > > > https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available

Re: [DISCUSS] making Ozone a separate Apache project

+1 -Akira On Wed, May 13, 2020 at 4:53 PM Elek, Marton wrote: > > > I would like to start a discussion to make a separate Apache project for > Ozone > > > > ### HISTORY [1] > > * Apache Hadoop Ozone development started on a feature branch of > Hadoop repository (HDFS-7240) > > * In the

Re: Precommit job fails to write comments in the GitHub pull requests

> Can we point to a commit before Yetus-994 instead of master and get away with > this? I'm fine with that approach not to breaking more. Filed https://issues.apache.org/jira/browse/HADOOP-17297 Thanks, Akira On Mon, Oct 5, 2020 at 10:18 AM Akira Ajisaka wrote: > > Hi Masta

Re: Precommit job fails to write comments in the GitHub pull requests

ain in order to > > avoid surprising the developers. > > We can upgrade Yetus when JDK11 Javadoc issue is fixed. > > > > Regards, > > Masatake Iwasaki > > > >> On 2020/09/29 2:55, Akira Ajisaka wrote: > >> Apache Hadoop developers, > >>

Re: [DISCUSS] fate of branch-2.9

+1 Thanks, Akira On Fri, Aug 28, 2020 at 5:51 PM lisheng.sun08 wrote: > +1 on EOL of branch-2.9. > > Thanks, > Lisheng Sun > > > > 发自我的小米手机 > 在 2020年8月27日 下午1:55，Wei-Chiu Chuang 写道： > > Bump up this thread after 6 months. > > Is anyone still interested in the 2.9 release line? Or are we good

Re: Precommit job fails to write comments in the GitHub pull requests

I've got a GitHub App token from the infra team and set this to the hadoop-multibranch job. The commit statuses in GitHub pull requests will be updated by Jenkins and you'll need to check these statuses. -Akira On Tue, Sep 29, 2020 at 2:55 AM Akira Ajisaka wrote: > > Apache Hadoop deve

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

+1 Thanks, Akira On Fri, Sep 25, 2020 at 3:00 PM Elek, Marton wrote: > > Hi all, > > Thank you for all the feedback and requests, > > As we discussed in the previous thread(s) [1], Ozone is proposed to be a > separated Apache Top Level Project (TLP) > > The proposal with all the details,

Precommit job fails to write comments in the GitHub pull requests

Apache Hadoop developers, After YETUS-994, the jenkins job updates the commit status instead of writing a comment to the pull request. It requires an OAuth token with write access to "repo:status" but now there is no such token for Apache Hadoop. I asked the infra team to create a token:

Re: [VOTE] Release Apache Hadoop 3.3.0 - RC0

+1 (binding) - Verified checksums and signatures. - Built from the source with CentOS 7 and OpenJDK 8. - Successfully upgraded HDFS to 3.3.0-RC0 in our development cluster (with RBF, security, and OpenJDK 11) for end-users. No issues reported. - The document looks good. - Deployed pseudo cluster

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

Hi Gabor, Thank you for your work! Kihwal reported IBR leak in standby NameNode: https://issues.apache.org/jira/browse/HDFS-15421. I think this is a blocker and this affects 3.1.4-RC1. Would you check this? Best regards, Akira On Mon, Jun 22, 2020 at 10:26 PM Gabor Bota wrote: > Hi folks, >

Re: Moving to Yetus 0.12.0

Updated Yetus version to 0.12.0 in branch-2.10 qbt job: https://builds.apache.org/view/H-L/view/Hadoop/job/hadoop-qbt-branch-2.10-java7-linux-x86/ -Akira On Tue, Apr 28, 2020 at 6:59 AM Akira Ajisaka wrote: > Hi folks, > > After upgrading the image from Ubuntu 16.04 to Ubuntu 18.04

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC3

I found TestCombineFileInputFormat is failing in branch-3.2.2 and I've cherry-picked MAPREDUCE-7284 to fix the failure. Thanks, Akira On Fri, Dec 4, 2020 at 9:09 AM Chao Sun wrote: > > Thanks Xiaoqiao. I just committed the fix to branch-3.2 (and will port it > to other branches as well later).

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC3

In addition, backported HDFS-13404 to fix TestRouterWebHDFSContractAppend failure. On Fri, Dec 4, 2020 at 10:43 AM Akira Ajisaka wrote: > > I found TestCombineFileInputFormat is failing in branch-3.2.2 and I've > cherry-picked MAPREDUCE-7284 to fix the failure. > > Thanks, >

[DISCUSS] Upgrading Jersey from 1.x

Hi folks, Recently I resumed the work for upgrading Jersey: - https://issues.apache.org/jira/browse/HADOOP-15984 - https://github.com/apache/hadoop/pull/763 This upgrade is important because we cannot compile and run Jersey 1.x with Java 11+. However, it is very complicated because: 1. We need

Fixing flaky tests in Apache Hadoop

Hi Hadoop developers, Now there are a lot of failing unit tests and there is an issue to tackle this bad situation. https://issues.apache.org/jira/browse/HDFS-15646 Although this issue is in HDFS project, this issue is related to all the Hadoop developers. Please check the above URL, read the

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC1

-1 - YARN resource localization is broken by HADOOP-17306 and it has been reverted. It should be reverted from 3.2.2 as well. (Thank you Jim Brennan for the report!) - Would you include HDFS-15643 in RC2? This fixes checksum error in EC with ISA-L. Thank you He Xiaoqiao for preparing the release

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC5

+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 Thanks, Akira On Sun, Jan 3, 2021 at 11:40 PM Xiaoqiao He wrote: > > Hi folks, > >

Easy way to run all the unit tests (apache id required)

Hi folks, I've prepared a Jenkins on-demand qbt job: https://ci-hadoop.apache.org/job/hadoop-qbt-any-java8-linux-x86_64 If you are tired of touching the source code in the modules to run all the tests (and seeing some broken Jenkins job results), please use this job instead. How to use: - Login

Re: [VOTE] Release Apache Hadoop 3.2.2 - RC4

o Sun > HADOOP-15775. [JDK9] Add missing javax.activation-api dependency. > Contributed by Akira Ajisaka. > HDFS-15240. Erasure Coding: dirty buffer causes reconstruction block error. > Contributed by HuangTao. > HDFS-15708. TestURLConnectionFactory fails by NoClassDefFoundError in &g

Re: [VOTE] Hadoop 3.1.x EOL

This vote has passed with 18 binding +1. I'll update the JIRA and the wiki. Thanks all for your participation. On Tue, Jun 8, 2021 at 3:03 AM Steve Loughran wrote: > > > > On Thu, 3 Jun 2021 at 07:14, Akira Ajisaka wrote: >> >> Dear Hadoop developers, >&

Re: [VOTE] hadoop-thirdparty 1.1.0-RC0

+1 - Verified checksums and signatures - Built from source with -Psrc profile - Checked the documents -Akira On Thu, May 13, 2021 at 8:55 PM Wei-Chiu Chuang wrote: > > Hello my fellow Hadoop developers, > > I am putting together the first release candidate (RC0) for > Hadoop-thirdparty 1.1.0.

Re: [DISCUSS] Change project style guidelines to allow line length 100

I'm +1 to allow <= 100 chars. FYI: There were some discussions long before: - https://lists.apache.org/thread.html/7813c2f8a49b1d1e7655dad180f2d915a280b2f4d562cfe981e1dd4e%401406489966%40%3Ccommon-dev.hadoop.apache.org%3E -

Re: [DISCUSS] which release lines should we still consider actively maintained?

Hi Sean, Thank you for starting the discussion. I think branch-2.10, branch-3.1, branch-3.2, branch-3.3, and trunk (3.4.x) are actively maintained. The next releases will be: - 3.4.0 - 3.3.1 (Thanks, Wei-Chiu!) - 3.2.3 - 3.1.5 - 2.10.2 > Are there folks willing to go through being release

Re: [VOTE] Release Apache Hadoop Thirdparty 1.1.1 RC0

+1 - Verified checksums and signatures - Built from source with -Psrc profile - Checked the documents - Compiled Hadoop trunk and branch-3.3 with Hadoop third-party 1.1.1. -Akira On Wed, May 26, 2021 at 5:29 PM Wei-Chiu Chuang wrote: > > Hi folks, > > I have put together a release candidate

[VOTE] Hadoop 3.1.x EOL

Dear Hadoop developers, Given the feedback from the discussion thread [1], I'd like to start an official vote thread for the community to vote and start the 3.1 EOL process. What this entails: (1) an official announcement that no further regular Hadoop 3.1.x releases will be made after 3.1.4.

Re: [DISCUSS] which release lines should we still consider actively maintained?

gt;> > >> > >> For Hadoop 3.3 line: If no one beats me, I plan to make a 3.3.2 in 2-3 > >> months. And another one in another 2-3 months. > >> The Hadoop 3.3.1 has nearly 700 commits not in 3.3.0. It is very difficult > >> to make/validate a maint releas

Re: Hadoop-3.2.3 Release Update

Thanks Brahma for cutting branch-3.2.3. In Apache Bigtop, there are some patches applied to Hadoop 3.2.2. https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common/hadoop In these patches, how about backporting the following issues to branch-3.2 and branch-3.2.3? - HADOOP-14922 -

Re: [DISCUSS] Hadoop 3.2.3 release

t 2:05 PM Xiaoqiao He wrote: >> >> >> >>> Thanks Brahma for volunteering and driving this release plan. I just >> >>> created a dashboard for 3.2.3 release[1]. >> >>> I would like to support for this release line if need. (cc Brahma) >> >>

Re: [DISCUSS] Migrate to Yetus Interface classification annotations

Hi Masatake, The problem comes from the removal of com.sun.tools.doclets.* packages in Java 10. In Apache Hadoop, I removed the doclet support for filtering javadocs when the environment is Java 10 or upper. https://issues.apache.org/jira/browse/HADOOP-15304 Thanks, Akira On Tue, Sep 28, 2021

Re: Hadoop-3.2.3 Release Update

Battula >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> Waiting for the following jira to commit to hadoop-3.2.3 , mostly this >>>>> can >>>>> be done by this week,then I will try to create the RC next if there is >>

Re: [VOTE] Release Apache Hadoop 3.3.2 - RC0

Hi Chao, > For this, I just need to update the hadoop-project/src/site/markdown/index.md.vm and incorporate notable changes made in 3.3.1/3.3.2, is that correct? > ARM binaries There was a discussion [1] and concluded that ARM binaries are optional. The release vote is only for source code, not

Re: [VOTE] Release Apache Hadoop 3.3.2 - RC0

Thank you Chao Sun for preparing the RC. I've added your public key to the Hadoop KEYS file ( https://downloads.apache.org/hadoop/common/KEYS). Thanks, Akira On Fri, Dec 10, 2021 at 11:10 AM Chao Sun wrote: > Hi all, > > Sorry for the long delay. I've prepared RC0 for Hadoop 3.3.2 below: > >

Re: [DISCUSS] Change project style guidelines to allow line length 100

Based on the positive feedback, filed https://issues.apache.org/jira/browse/HADOOP-17813 to update the checkstyle rule. I don't think it requires a vote thread. Thanks and regards, Akira On Sun, Jun 13, 2021 at 1:14 AM Steve Loughran wrote: > > +1 > > if you look closely the hadoop-azure module

[DISCUSS] Hadoop 3.2.3 release

Hi all, Hadoop 3.2.2 was released half a year ago, and now, we have accumulated more than 230 commits [1]. Therefore I want to start the release work for 3.2.3. There is one blocker for 3.2.3 [2]. - https://issues.apache.org/jira/browse/HDFS-12920 Is there anyone who would volunteer to be the

Re: [DISCUSS] Hadoop 3.2.3 release

Hi Brahma, Thank you for volunteering! -Akira On Fri, Jul 23, 2021 at 5:57 PM Brahma Reddy Battula wrote: > > Hi Akira, > > Thanks for bringing this.. > > I want to drive this if nobody already plan to do this.. > > > On Thu, 22 Jul 2021 at 8:48 AM, Akira A

Re: Possibility of using ci-hadoop.a.o for Nutch integration tests

(Adding builds@) Hi Lewis, Nutch is already using ci-builds.apache.org, so I think Nutch can continue using it. ci-hadoop.apache.org provides almost the same functionality as ci-builds.apache.org and there is no non-production Hadoop cluster running there. Therefore moving to ci-hadoop does not

Re: [DISCUSS] Hadoop 2.10.2 release

Thank you Masatake. +1 to release 2.10.2. On Fri, Mar 4, 2022 at 6:52 PM Masatake Iwasaki wrote: > Hi team, > > There are over 170 fixed issues in branch-2.10 after the release of > 2.10.1[1]. > Given that there is still a need for 2.10.x, I would like to release 2.10.2 > after HADOOP-18088[2]

Re: [VOTE] Release Apache Hadoop 3.2.3 - RC1

+1 (binding) - Verified the signatures and the checksums - Built from source using the "start-build-env.sh" from Ubuntu laptop. - Setup pseudo cluster and ran some mapreduce jobs. - Checked the Web UIs and the daemon logs. Thanks, Akira On Sun, Mar 20, 2022 at 2:33 PM Masatake Iwasaki <

[NOTICE] Attaching patches in JIRA issue no longer works

Dear Hadoop developers, I've disabled the Precommit-(HADOOP|HDFS|MAPREDUCE|YARN)-Build jobs. If you attach a patch to a JIRA issue, the Jenkins precommit job won't run. Please use GitHub PR for code review. Background: - https://issues.apache.org/jira/browse/HADOOP-17798 -

<    1   2   3   4   >