I'm waiting for a git update of trunk to complete, not having done it since
last week. The 1.8 GB download is taking a long time over a VPN.
Updating files: 100% (8518/8518), done.
Switched to branch 'trunk'
Your branch is up to date with 'apache/trunk'.
remote: Enumerating objects: 4142992,
s, with 4 votes binding
> and
> > 1 vote non-binding.
> >
> > Thank you very much for voting and verifying!
> >
> > This voting will continue until March 15th, this Friday.
> >
> > Best Regards,
> > Shilun Fan.
> >
> > On Tue, Mar 1
+1 binding
(sorry, this had ended in the yarn-dev folder, otherwise I'd have seen it
earlier. been testing it this afternoon:
pulled the latest version of
https://github.com/apache/hadoop-release-support
(note, this module is commit-then-review; whoever is working on/validating
a release can
+1 for cutting hbase 1; it only reduces dependency pain (no more protobuf
2.5!)
Created the JIRA on that a few days back
https://issues.apache.org/jira/browse/YARN-11658
On Tue, 5 Mar 2024 at 12:08, Bryan Beaudreault
wrote:
> Hbase v1 is EOL for a while now, so option 2 probably makes sense.
Steve Loughran created YARN-11658:
-
Summary: ATS to make minimum HBase version 2.x
Key: YARN-11658
URL: https://issues.apache.org/jira/browse/YARN-11658
Project: Hadoop YARN
Issue Type
[
https://issues.apache.org/jira/browse/YARN-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11657.
---
Fix Version/s: 3.3.9
3.4.1
3.5.0
Resolution
hich should meet expectations.
>>
>> We also look forward to other members helping to verify.
>>
>> Best Regards,
>> Shilun Fan.
>>
>> On Fri, Feb 16, 2024 at 12:22 AM Steve Loughran
>> wrote:
>>
>> >
>> >
>> > On
Steve Loughran created YARN-11657:
-
Summary: Remove protobuf-2.5 as dependency of hadoop-yarn-api
Key: YARN-11657
URL: https://issues.apache.org/jira/browse/YARN-11657
Project: Hadoop YARN
On Mon, 12 Feb 2024 at 15:32, slfan1989 wrote:
>
>
> Note, because the arm64 binaries are built separately on a different
> platform and JVM, their jar files may not match those of the x86
> release -and therefore the maven artifacts. I don't think this is
> an issue (the ASF actually releases
so it'll have the s3a checksum and region stuff? that'd be wonderful! I've
been assuming i'd have to push out a 3.4.1 release for that alone.
On Sat, 10 Feb 2024 at 23:36, slfan1989 wrote:
> We will end the voting for hadoop-3.4.0-RC1 and will open the voting for
> hadoop-3.4.0-RC2 in 1-2 days.
-1 I'm afraid, just due to staging/packaging issues.
This took me a few goes to get right myself, so nothing unusual.
Note I used my validator project which is set to retrieve binaries, check
signatures, run maven builds against staged artifacts *and clean up any
local copies first*and more.
wonderful! I'll be testing over the weekend
Meanwhile, new changes I'm putting in to trunk are tagged as fixed in 3.5.0
-correct?
steve
On Thu, 11 Jan 2024 at 05:15, slfan1989 wrote:
> Hello all,
>
> We plan to release hadoop 3.4.0 based on hadoop trunk, which is the first
> hadoop 3.4.0-RC
+1
On Wed, 6 Dec 2023 at 04:09, Xiaoqiao He wrote:
> Dear Hadoop devs,
>
> Given the feedback from the discussion thread [1], I'd like to start
> an official thread for the community to vote on release line 3.2 EOL.
>
> It will include,
> a. An official announcement informs no further regular
+1 for making 3.3 and 3.4 the maintained lines
3.2.x we should say -as it is true- that the age of the dependencies is
such that it is transitively insecure. To fix those, people must upgrade.
For 2.10.x, we should think about whether to cherrypick our own CVEs there,
but not actually do any new
Can anyone from yarn or hdfs review this before i just upvote it hoping all
will be well. thanks
-- Forwarded message -
From: PJ Fanning (Jira)
Date: Wed, 11 Oct 2023 at 20:27
Subject: [jira] [Created] (HADOOP-18933) upgrade netty to 4.1.100 due to CVE
To:
PJ Fanning created
can we get some reviews from users of grpc/netty code here. otherwise i'd
upvoting without knowing what will break. thanks
-- Forwarded message -
From: PJ Fanning (Jira)
Date: Mon, 9 Oct 2023 at 11:46
Subject: [jira] [Created] (HADOOP-18924) upgrade grpc jars to v1.53.0 due
to
[
https://issues.apache.org/jira/browse/YARN-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-10992.
---
Resolution: Cannot Reproduce
trunk seems to build on java17 now...
> schema generat
Steve Loughran created YARN-11546:
-
Summary: NPE in TestTimelineAuthFilterForV2
Key: YARN-11546
URL: https://issues.apache.org/jira/browse/YARN-11546
Project: Hadoop YARN
Issue Type: Bug
could be good.
why not set it up for the third-party module first to see how well it works?
On Tue, 18 Jul 2023 at 21:05, Ayush Saxena wrote:
> Something we can explore as well!!
>
> -Ayush
>
> Begin forwarded message:
>
> > From: Volkan Yazıcı
> > Date: 19 July 2023 at 1:24:49 AM IST
> > To:
i've seen the npm complaints too, but it wasn't something I wanted to go
near.
Which modules use the NPM artifacts, and who is using them in production?
As if they are orphan, we need to discuss what to do.
On Tue, 27 Jun 2023 at 21:59, Wei-Chiu Chuang wrote:
> Hi,
>
> First of all, I am not
1. we should patch gcs, to ignore those new keys.
2. i may be able to validate RC1 this weekend
On Fri, 16 Jun 2023 at 03:20, Wei-Chiu Chuang
wrote:
> Overall so far so good.
>
> hadoop-api-shim:
> built, tested successfully.
>
> cloudstore:
> built successfully.
>
> Spark:
> built
Which branch is -3.3.6 off? 3.3.5 or 3.3?
I'm travelling for the next few days and unlikely to be able to test this;
will do my best
On Wed, 14 Jun 2023 at 07:27, Wei-Chiu Chuang wrote:
> I am inviting anyone to try and vote on this release candidate.
>
> Note:
> This is built off branch-3.3.6
Wei-Chiu has suggested a minimal "things in 3.3.5 which were very broken,
api change for ozone and any critical jar updates"
so much lower risk/easier to qualify and ship.
I need to get https://issues.apache.org/jira/browse/HADOOP-18724 in here;
maybe look at a refresh of the "classic" jars
can disable it. Will do it
> tomorrow, if nobody objects. In case the one who configured it wants
> to do it early, feel free to do so.
>
> We already have one for branch-3.3 which runs weekly which most
> probably most of us don't follow :)
>
> -Ayush
>
> On Wed, 22 Mar 2023 at 00:
ing major dependency upgrades (log4j 1 to 2, jersey 1
> to 2 and junit 4 to 5) are blockers for java 11 compile + test stability.
>
>
> On Tue, Mar 28, 2023 at 4:55 AM Steve Loughran >
> wrote:
>
> > Now that hadoop 3.3.5 is out, i want to propose something new
> >
On behalf of the Apache Hadoop Project Management Committee, I am
pleased to announce the release of Apache Hadoop 3.3.5.
This is a release of Apache Hadoop 3.3 line.
Key changes include
* A big update of dependencies to try and keep those reports of
transitive CVEs under control -both
ok, here's my summary, even though most of the binding voters forgot to
declare they were on the PMC.
+1 binding
Steve Loughran
Chris Nauroth
Masatake Iwasaki
Ayush Saxena
Xiaoqiao He
+1 non-binding
Viraj Jasani
0 or -1 votes: none.
Accordingly: the release is good!
I will send the formal
with scale profile looks good
>
>
> On Wed, Mar 15, 2023 at 12:48 PM Steve Loughran
>
> wrote:
>
> > Apache Hadoop 3.3.5
> >
> > Mukund and I have put together a release candidate (RC3) for Hadoop
> 3.3.5.
> >
> > What we would like is for an
so
ISA-L: false libhadoop was built without ISA-L support
PMDK:false The native code was built without PMDK support.
---
On Wed, 15 Mar 2023 at 19:47, Steve Loughran wrote:
>
> Apache Hadoop 3.3.5
>
> Mukund and I have put together a release candidate (RC3) for Hadoop 3.3.5.
&g
Apache Hadoop 3.3.5
Mukund and I have put together a release candidate (RC3) for Hadoop 3.3.5.
What we would like is for anyone who can to verify the tarballs, especially
anyone who can try the arm64 binaries as we want to include them too.
The RC is available at:
Steve Loughran created YARN-11454:
-
Summary: high-entropy abfs/https proxy passwords don't make it
through to yarn/mr worker processes
Key: YARN-11454
URL: https://issues.apache.org/jira/browse/YARN-11454
not exist (#5400) [ZanderXu <
> zande...@apache.org
> >]
> * 44bf8aadedf 2023-03-03 HDFS-16832. [SBN READ] Follow-on to HDFS-16732.
> Fix NPE when check the block location of empty directory (#5099)
> [zhengchenyu ]
> * 72f8c2a4888 (tag: release-3.3.5-RC2) 2023-02-25 HADOOP-18641. Clo
gt;
>
> On Sat, Mar 4, 2023 at 4:29 AM Steve Loughran >
> wrote:
>
> > On Sat, 4 Mar 2023 at 01:47, Erik Krogen wrote:
> >
> > > Thanks Steve. I see now that the branch cut was way back in October so
> I
> > > definitely understand your frustratio
> >> * Built tar from source (1.8.0_341): ok
>> >> - mvn clean package -Pdist -DskipTests -Dtar
>> -Dmaven.javadoc.skip=true
>> >>
>> >> * Built images using the tarball, installed and started all of Hdfs,
>> JHS
>> >> and Yarn components
>&g
owCounter Mapreduce job
>> * Hdfs CRUD tests
>> * MapReduce wordcount job
>>
>> * Ran S3A tests with scale profile against us-west-2:
>> mvn clean verify -Dparallel-tests -DtestsThreadCount=8 -Dscale
>>
>> ITestS3AConcurrentOps#testParallelRename is timing out a
[
https://issues.apache.org/jira/browse/YARN-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-10444.
---
Resolution: Fixed
came in with HADOOP-16202
> use openFile() with sequential
erging to branch-3.3.5 as well.
>
> Thanks for the consideration and sorry for not bringing this up in RC1 or
> earlier.
>
> On Mon, Feb 27, 2023 at 9:59 AM Steve Loughran >
> wrote:
>
> > Mukund and I have put together a release candidate (RC2) for Hadoop
> 3.3.
Mukund and I have put together a release candidate (RC2) for Hadoop 3.3.5.
We need anyone who can to verify the source and binary artifacts,
including those JARs staged on maven, the site documentation and the arm64
tar file.
The RC is available at:
without that file being up to
date, but at least all the transitive stuff is correctly licensed. And i
think we need to change the PR template to mention transitive updates in
the license bit too
if this goes in, I will do the rebuild on monday UK time
On Thu, 23 Feb 2023 at 11:18, Steve Loughran
. Going to
revert HADOOP-18590. Publish SBOM artifacts (#5281)
On Thu, 23 Feb 2023 at 10:29, Steve Loughran wrote:
> ok, let me cancel, update those jiras and kick off again. that will save
> anyone else having to do their homework
>
> On Thu, 23 Feb 2023 at 08:56, Takanobu Asan
16310
> > - HADOOP-18014
> >
> > I corrected all the wrong fix versions just now. I'm not sure we should
> > revote it since it only affects the changelog.
> >
> > - Takanobu
> >
> > 2023年2月21日(火) 22:43 Steve Loughran :
> >
> >> Apache Hadoop
[
https://issues.apache.org/jira/browse/YARN-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11394.
---
Fix Version/s: 3.4.0
Resolution: Fixed
> Fix hadoop-yarn-server-resourcemana
Apache Hadoop 3.3.5
Mukund and I have put together a release candidate (RC1) for Hadoop 3.3.5.
What we would like is for anyone who can to verify the tarballs, especially
anyone who can try the arm64 binaries as we want to include them too.
The RC is available at:
[
https://issues.apache.org/jira/browse/YARN-11441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11441.
---
Fix Version/s: 3.4.0
3.3.5
Resolution: Done
> Revert YARN-10
Steve Loughran created YARN-11441:
-
Summary: Revert YARN-10495
Key: YARN-11441
URL: https://issues.apache.org/jira/browse/YARN-11441
Project: Hadoop YARN
Issue Type: Task
thanks
pulling in a few of the recent changes which seem needed/important, now
wondering about the javadocs.
i will add a new probe for this in our automated release ant bulld so we
can't cut a release without that
https://github.com/steveloughran/validate-hadoop-client-artifacts
On Mon, 2 Jan
Mukund and I have put together a release candidate (RC0) for Hadoop 3.3.5.
Given the time of year it's a bit unrealistic to run a 5 day vote and
expect people to be able to test it thoroughly enough to make this the one
we can ship.
What we would like is for anyone who can to verify the
The first "smoke test" RC is about to be up for people to play with, we are
just testing things here and getting that arm build done.
Can I have some content for the index.html page describing what has changed?
hadoop-project/src/site/markdown/index.md.vm
I can (and will) speak highly of stuff
[
https://issues.apache.org/jira/browse/YARN-11330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11330.
---
Fix Version/s: 3.4.0
3.3.5
Resolution: Fixed
> Use secure
[
https://issues.apache.org/jira/browse/YARN-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11039.
---
Fix Version/s: 3.4.0
3.3.5
Resolution: Fixed
merged in the hadoop
ed tuning
fixed now HADOOP-18401
>
>
> On Tue, Sep 27, 2022 at 9:35 AM Steve Loughran >
> wrote:
>
> > Mukund has just created the new Hadoop release JIRA,
> > https://issues.apache.org/jira/browse/HADOOP-18470, and is doing the
> first
> > build/test befo
there's a PR up to update jettison, which is only used by yarn rm and nm
https://issues.apache.org/jira/browse/HADOOP-18468
reviews welcome, as if things break it'll be yarn that stops working.
of course, if someone actually wants to help coalesce the #of json
libraries used across the project
Mukund has just created the new Hadoop release JIRA,
https://issues.apache.org/jira/browse/HADOOP-18470, and is doing the first
build/test before pushing it up. This is off branch-3.3, so it will have
more significant changes than the 3.3.3 and 3.3.4 releases, which were just
CVE/integration
Hi
Mukund Thakur plans to fork off the next branch-3.3. release in 10 days
time. last chance to get changes in.
I'm away next week...try not to break the branch. Any testing you can do
would be appreciated
Steve
On behalf of the Apache Hadoop Project Management Committee, I am
pleased to announce the release of Apache Hadoop 3.3.4.
---
This is a release of Apache Hadoop 3.3 line.
It contains a small number of security and critical integration fixes since
3.3.3.
Users of Apache Hadoop 3.3.3 should
on top
> of it and all passed. Did some kills, stuff came back.
>
> I didn't spend time on unit tests but one set passed on a local rig here:
>
> [image: image.png]
> Stack
>
> On Fri, Jul 29, 2022 at 11:48 AM Steve Loughran
> wrote:
>
>> I have put together a rel
The vote passed with the following result.
Binding PMC members:
+1 Chris Nauroth
+1 Steve Loughran
+1 Masatake Iwasaki
Non binding votes:
+1 Ashutosh Gupta
Cheng Pan was worried about the new transient kotlin dependency. They are
working on a PR there which we can target for the successor
local projects
https://github.com/steveloughran/validate-hadoop-client-artifacts
all good as far as my test coverage goes, with these projects validating
the staged dependencies.
now, who else can review
On Fri, 29 Jul 2022 at 19:47, Steve Loughran wrote:
>
>
> I have put together
I have put together a release candidate (RC1) for Hadoop 3.3.4
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC1/
The git tag is release-3.3.4-RC1, commit a585a73c3e0
The maven artifacts are staged at
Jul 2022 at 19:07, Steve Loughran wrote:
>
> I have put together a release candidate (RC0) for Hadoop 3.3.4
>
> The RC is available at:
> https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC0/
>
> The git tag is release-3.3.4-RC0, commit c679bc76d26
>
> The
I have put together a release candidate (RC0) for Hadoop 3.3.4
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.3.4-RC0/
The git tag is release-3.3.4-RC0, commit c679bc76d26
The maven artifacts are staged at
[
https://issues.apache.org/jira/browse/YARN-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11193.
---
Resolution: Invalid
> hadoop-yarn-common jquery js file lacks approved hea
Steve Loughran created YARN-11193:
-
Summary: jquery js file lacks approved header
Key: YARN-11193
URL: https://issues.apache.org/jira/browse/YARN-11193
Project: Hadoop YARN
Issue Type: Bug
:02, Steve Loughran wrote:
> I'm setting things up for a new release
>
> https://issues.apache.org/jira/browse/HADOOP-18305
>
> absolute minimum of fixes. as well as some related to ZK lockdown, i would
> like to include
>
> https://issues.apache.org/jira/browse/HADOO
I'm setting things up for a new release
https://issues.apache.org/jira/browse/HADOOP-18305
absolute minimum of fixes. as well as some related to ZK lockdown, i would
like to include
https://issues.apache.org/jira/browse/HADOOP-18303
remove shading exclusion of javax.ws.rs-api from
Steve Loughran created YARN-11189:
-
Summary: TestLocalDistributedCacheManager failing after
HADOOP-16202
Key: YARN-11189
URL: https://issues.apache.org/jira/browse/YARN-11189
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11172.
---
Fix Version/s: 3.4.0
3.3.4
Resolution: Fixed
>
Steve Loughran created YARN-11173:
-
Summary: update os-maven-plugin to 1.7.0 in yarn-csi
Key: YARN-11173
URL: https://issues.apache.org/jira/browse/YARN-11173
Project: Hadoop YARN
Issue Type
I want to start a quick discussion on a plan for hadoop releases this
summer. I am willing to do the release manager work. Mukund and Mehakmeet
have have already volunteered to help even if they don't know that yet.
I've got two goals
1. minor followup to 3.3.3
2. feature release of new
+1 binding
I've extended my validator project
https://github.com/steveloughran/validate-hadoop-client-artifacts
it now
* fetches KEYS
* fetches an RC from a remote url
* validates signing
* untars and tries to build source
* untars binary release and tries some native commands
the source build
On behalf of the Apache Hadoop Project Management Committee, I'm pleased to
announce that Hadoop 3.3.3 has been
released:
https://hadoop.apache.org/release/3.3.3.html
This is the third stable release of the Apache Hadoop 3.3 line.
It contains 23 bug fixes, improvements and enhancements since
t;
> > > > Thanks Steve for your work.
> > > >
> > > > - He Xiaoqiao
> > > >
> > > > On Mon, May 16, 2022 at 4:25 AM Viraj Jasani
> > wrote:
> > > > >
> > > > > +1 (non-binding)
> > >
I have put together a release candidate (RC1) for Hadoop 3.3.3
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC1/
The git tag is release-3.3.3-RC1, commit d37586cbda3
The maven artifacts are staged at
a version in staging with the files; still don't know how the
previous delete lacked them, I will do more testing tomorrow before putting
up the next RC. which will be off the same git commit as before, just a
rebuild, repackage and republish.
-Steve
On Tue, 10 May 2022 at 00:18, Steve Loughran
https://repository.apache.org/content/repositories/staging/
>
>
> true
>
>
> true
>
>
>
> to the `` section in your Maven pom.xml file.
>
> On Mon, May 9, 2022 at 8:52 AM Steve Loughran
> wrote:
> >
>>>
> >>>>>> * Signature: ok
> >>>>>> * Checksum : passed
> >>>>>> * Rat check (1.8.0_191): passed
> >>>>>>- mvn clean apache-rat:check
> >>>>>> * Built from source (1.8.0_191): faile
compensate for this time.
> >>
> >> For now lets just integrate it our nightly builds only and circle back
> >> again here in future if the need be.
> >>
> >> -Ayush
> >>
> >>> On Fri, 6 May 2022 at 20:44, Wei-Chiu Chuang
> wro
kipTests
> > >>>> - mvn -fae --no-transfer-progress -DskipTests
> > -Dmaven.javadoc.skip=true
> > >>>> -Pnative -Drequire.openssl -Drequire.snappy -Drequire.valgrind
> > >>>> -Drequire.zstd -Drequire.test.libhadoop clean i
I'm not enthusiastic here as it not only makes the builds slower, it
reduces the #of builds we can through a day
one thing I am wondering is could we remove java8 support on some branches?
make branch 3.3.2.x (i.e the 3.3.3 release) the last java 8 build, and this
summers branch-3.3 release
Whenever I push I commit to github it warns that there are lots of
vulnerabilities in dependencies. When I look at those mostly they are in
.js files pulled in by the yarn ui.
Is there any active work keeping these dependencies up to date?
I am thinking of doing a new hadoop release this summer
I have put together a release candidate (rc0) for Hadoop 3.3.3
The RC is available at:
https://dist.apache.org/repos/dist/dev/hadoop/3.3.3-RC0/
The git tag is release-3.3.3-RC0, commit d37586cbda3
The maven artifacts are staged at
[
https://issues.apache.org/jira/browse/YARN-11075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11075.
---
Fix Version/s: 3.3.3
(was: 3.4.0)
(was: 3.3.4
[
https://issues.apache.org/jira/browse/YARN-11014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-11014.
---
Fix Version/s: 3.3.3
(was: 3.4.0)
(was: 3.3.4
[
https://issues.apache.org/jira/browse/YARN-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-10720.
---
Fix Version/s: 3.3.3
Resolution: Fixed
FIxed in 3.3.3; updating fix versions
There is now a branch-3.3.3 in the repo; this is forked off 3.3.2, *not*
branch-3.3
branch-3.3 has its hadoop version now set to 3.3.4
I've renamed the release version 3.3.3 in JIRA to 3.3.4, so all
fixed/target/affects references have been automatically updated. text
references in JIRAs and PRs
vulnerabilities which were never reached in the Hadoop code, but which
audit tools would flag up.
I'd also like to update our shaded protobuf library too
On Mon, 11 Apr 2022 at 14:54, Steve Loughran wrote:
>
> I've just created a new JIRA and assigned to myself: HADOOP-18198. Release
&g
I've just created a new JIRA and assigned to myself: HADOOP-18198. Release
Hadoop 3.3.3: hadoop-3.3.2 with CVE fixes
https://issues.apache.org/jira/browse/HADOOP-18198
--
Hadoop 3.3.3 is a minor followup release to Hadoop 3.3.2 with
* CVE fixes in Hadoop source
* CVE fixes in
maybe even before moving the catalog away, we could make it optional
On Fri, 28 Jan 2022 at 08:24, Akira Ajisaka wrote:
> Thank you Masatake and Chao!
>
> On Fri, Jan 28, 2022 at 5:11 PM Chao Sun wrote:
>
> > Thanks Masatake and Akira for discovering the issue. I used
> >
that error
org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-default-http-blocker (
http://0.0.0.0/): Blocked mirror for repositories: [maven-restlet
implies maven is not downloading http artifacts, and it had decided that
the reslet artifacts were coming off an http repo, even though its in
fix is in t disable auditing, which is now the default
https://issues.apache.org/jira/browse/HADOOP-18094
everything is OK for apps which retain the same fs instances for the life
of the app, but not for Hive...
will do a better fix ASAP where in exchange for loss of auditing after a GC
event,
`now some bad news
https://issues.apache.org/jira/browse/HADOOP-18091
S3A auditing leaks memory through ThreadLocal references
surfaces in processes with long lived threads creating and destroying many
s3a FS instances.
working on a fix right now
On Fri, 21 Jan 2022 at 21:02, Eric Payne
wrote:
*+1 binding.*
reviewed binaries, source, artifacts in the staging maven repository in
downstream builds. all good.
*## test run*
checked out the asf github repo at commit 6da346a358c into a location
already set up with aws and azure test credentials
ran the hadoop-aws tests with
On Thu, 20 Jan 2022 at 17:15, Andrew Purtell
wrote:
> Just to clarify: I think you want to upgrade to Log4J2 (or switch to
> LogBack) as a strategy for new releases, but you have the option in
> maintenance releases to use Reload4J to maintain Appender API and
> operational compatibility, and
thanks, i'm on it..will run the aws and azure tests and then play with the
artifacts
On Wed, 19 Jan 2022 at 17:50, Chao Sun wrote:
> Hi all,
>
> I've put together Hadoop 3.3.2 RC2 below:
>
> The RC is available at:
> http://people.apache.org/~sunchao/hadoop-3.3.2-RC2/
> The RC tag is at:
>
On Tue, 14 Dec 2021 at 22:56, Chao Sun wrote:
> Thanks all for taking a look! looks like we need another RC addressing the
> following issues.
>
> > 1. the overview page of the doc is for the Hadoop 3.0 release. It would
> be best to base the doc on top of Hadoop 3.3.0 overview page. (it's a
I'll do my best to test this; I'm a bit broken right now.
I think we should mention in a release notes that is the version of a log4j
included in this and all previous releases is not vulnerable. But provide a
list plus links to any that have been fixed
On Fri, 10 Dec 2021 at 02:09, Chao Sun
Steve Loughran created YARN-10992:
-
Summary: schema generation produces code which doesn't compile on
java 11+
Key: YARN-10992
URL: https://issues.apache.org/jira/browse/YARN-10992
Project: Hadoop
[
https://issues.apache.org/jira/browse/YARN-10988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-10988.
---
Resolution: Invalid
> Spark application stuck at ACCEPTED state at spark-sub
[
https://issues.apache.org/jira/browse/YARN-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved YARN-10941.
---
Resolution: Invalid
going to have to close this as invalid, sorry
# JIRA isn't the place
Steve Loughran created YARN-10878:
-
Summary: TestNMSimulator imports com.google.common.base.Supplier;
Key: YARN-10878
URL: https://issues.apache.org/jira/browse/YARN-10878
Project: Hadoop YARN
1 - 100 of 472 matches
Mail list logo
