[jira] [Resolved] (HADOOP-17158) Test timeout for ITestAbfsInputStreamStatistics#testReadAheadCounters

[ https://issues.apache.org/jira/browse/HADOOP-17158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-17158. - Fix Version/s: 3.4.0 Resolution: Fixed fixed in trunk; happy to cherrypick to -3

[jira] [Resolved] (HADOOP-17229) Test failure as failed request body counted in byte received metric - ITestAbfsNetworkStatistics#testAbfsHttpResponseStatistics

[ https://issues.apache.org/jira/browse/HADOOP-17229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-17229. - Fix Version/s: 3.4.0 Resolution: Fixed > Test failure as failed request body cou

[jira] [Resolved] (HADOOP-17189) add way for s3a to recognise buckets with "." in name and switch to path access

[ https://issues.apache.org/jira/browse/HADOOP-17189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-17189. - Fix Version/s: 3.4.0 Resolution: Won't Fix WONTFIXing this, as buckets with . in

[jira] [Created] (HADOOP-17250) ABFS: Allow random read sizes to be of buffer size

Sneha Vijayarajan created HADOOP-17250: -- Summary: ABFS: Allow random read sizes to be of buffer size Key: HADOOP-17250 URL: https://issues.apache.org/jira/browse/HADOOP-17250 Project: Hadoop Commo

Apache Hadoop qbt Report: branch-2.10+JDK7 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/50/ No changes -1 overall The following subsystems voted -1: asflicense hadolint jshint pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: c

[jira] [Created] (HADOOP-17251) Upgrade netty-all to 4.1.50.Final on branch-2.10

Masatake Iwasaki created HADOOP-17251: - Summary: Upgrade netty-all to 4.1.50.Final on branch-2.10 Key: HADOOP-17251 URL: https://issues.apache.org/jira/browse/HADOOP-17251 Project: Hadoop Common

Re: [DISCUSS] Hadoop 2.10.1 release

https://issues.apache.org/jira/issues/?jql=project%20in%20(HADOOP%2C%20HDFS%2C%20YARN%2C%20MAPREDUCE)%20AND%20%22Target%20Version%2Fs%22%20%3D%202.10.1%20and%20statusCategory%20!%3D%20Done There is no blocker/critical issues now. I updated the target version of issues without recent activities or

Re: [DISCUSS] Ozone TLP proposal

Hi Elek, 2. Following the path of Submarine, any existing Hadoop committers -- who are willing to contribute -- can ask to be included in the initial committer list without any additional constraints. (Edit the wiki, or send an email to this thread or to me). Thanks for Vinod to suggesting

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86_64

For more details, see https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/259/ [Sep 7, 2020 8:29:20 AM] (Adam Antal) YARN-9136. getNMResourceInfo NodeManager REST API method is not documented [Sep 7, 2020 9:39:03 AM] (Peter Bacsko) YARN-10411. Create an allowCreate flag for Map

How to manually trigger a PreCommit build for a github PR?

Hi, To trigger a PreCommit build without code change, I can make the JIRA status "Patch Available" and provide the JIRA number to "Build With Parameters" link . Not sure how to do that for a PR without a real c

[jira] [Created] (HADOOP-17252) Website to link to latest Hadoop wiki

Mingliang Liu created HADOOP-17252: -- Summary: Website to link to latest Hadoop wiki Key: HADOOP-17252 URL: https://issues.apache.org/jira/browse/HADOOP-17252 Project: Hadoop Common Issue Typ

Re: How to manually trigger a PreCommit build for a github PR?

Thanks Dinesh. This is very helpful. I will add this to the wiki page if this is the suggested way of doing it. On Tue, Sep 8, 2020 at 2:54 PM Dinesh Chitlangia wrote: > You could try doing an empty commit. > > git commit

Re: How to manually trigger a PreCommit build for a github PR?

Hi Mingliang, If by running Pre-Commit without any code change, you mean to say rerun jenkins, that means it ran once, you want to run it again without any code changes? If so, You can go to that PR build and click on replay. For example : Once logged in, if you click on the below link : https://ci

Re: How to manually trigger a PreCommit build for a github PR?

You could try doing an empty commit. git commit --allow-empty -m 'trigger new CI check' && git push Thanks, Dinesh On Tue, Sep 8, 2020 at 5:39 PM Mingliang Liu wrote: > Hi, > > To trigger a PreCommit build without code change, I can make the JIRA > status "Patch Available" and provide the J

[jira] [Created] (HADOOP-17253) Upgrade zookeeper to 3.4.14 on branch-2.10

Masatake Iwasaki created HADOOP-17253: - Summary: Upgrade zookeeper to 3.4.14 on branch-2.10 Key: HADOOP-17253 URL: https://issues.apache.org/jira/browse/HADOOP-17253 Project: Hadoop Common

[jira] [Created] (HADOOP-17254) Upgrade hbase to 1.2.6.1 on branch-2

Masatake Iwasaki created HADOOP-17254: - Summary: Upgrade hbase to 1.2.6.1 on branch-2 Key: HADOOP-17254 URL: https://issues.apache.org/jira/browse/HADOOP-17254 Project: Hadoop Common Issu