+ 1 (non-binding) -> verified all checksums -> build from source on JDK 17 -> ran hadoop-azure (ABFS) integration tests. All passing. -> verified release notes for major abfs and wasb changes.
Thanks a lot for driving this release. All the best Anuj Modi On Mon, Mar 30, 2026 at 2:32 AM Chris Nauroth <[email protected]> wrote: > +1 (binding) > > * Verified all checksums. > * Verified all signatures. > * Built from source, including native code on Linux. > * mvn clean package -Pnative -Psrc -Drequire.openssl -Drequire.snappy > -Drequire.zstd -DskipTests > * Tests passed. > * mvn --fail-never clean test -Pnative -Dparallel-tests > -Drequire.snappy -Drequire.zstd -Drequire.openssl > -Dsurefire.rerunFailingTestsCount=3 -DtestsThreadCount=8 > * ARM distro does contain ARM-compatible binaries, and hadoop checknative > -a is successful. > * All hadoop-gcp integration tests pass. > * Successfully built a full distro from source with all > hadoop-cloud-storage providers and their bundled dependencies. > * Manually tested several hadoop fs commands against a GCS bucket. > * Verified inclusion of latest lz4-java 1.10.4 upgrade in both x86 and ARM > binaries. > * Apache Pulsar pre-submits related to Hadoop integration are successful > with the new RC. > * https://github.com/apache/pulsar/pull/25402 > > I filed the following bugs for follow-up targeted to 3.5.1. I don't > consider any of these to be blockers for 3.5.0. > > HADOOP-19851: Update S3A GCS compatibility docs to point to hadoop-gcs > HADOOP-19852: hadoop-tos test failures due to reflection failure > HADOOP-19853: S3A integration test failures against GCS bucket > > Chris Nauroth > > > On Fri, Mar 27, 2026 at 2:08 PM Aaron Fabbri <[email protected]> wrote: > > > +1 (binding) > > I downloaded the release, verified the checksum, and installed on three > > containers. > > Ran some mapreduce examples which succeeded. > > > > Only did a quick sanity-check this time: I'm still getting back up to > speed > > on tools for more thorough testing. > > > > Thanks for all the hard work Chris! > > > > On Fri, Mar 27, 2026 at 2:02 PM Mukund Madhav Thakur < > [email protected] > > > > > wrote: > > > > > +1 (binding) > > > > > > Used hadoop-release-support to download and validate the checksums and > > gpg > > > keys.- All good. > > > Untar the source and maven build - all good. > > > Untar the binary and then added the aws bundle jar and run hadoop fs > > > command to access S3 buckets - All good. > > > git checkout the tag release and build and run s3a connector > integration > > > tests - Mostly good other than this new tests > > > ITestS3AFileSystemIsolatedClassloader failures mentioned below. > > > > > > Thanks Chris for working on the release. > > > > > > [*ERROR*] *Errors: * > > > > > > [*ERROR*] * > > > > > > > > > ITestS3AFileSystemIsolatedClassloader.defaultIsolatedClassloader:130->assertInNewFilesystem:103->createNewTestFs:78 > > > » LogConfiguration java.lang.IllegalStateException: Could not invoke > > public > > > final java.lang.ClassLoader java.lang.ClassLoader.getParent() on > > > > > > > > > org.apache.hadoop.fs.s3a.ITestS3AFileSystemIsolatedClassloader$CustomClassLoader@3e5ebdfe > > > with arguments [] (Caused by java.lang.IllegalStateException: Could not > > > invoke public final java.lang.ClassLoader > > java.lang.ClassLoader.getParent() > > > on > > > > > > > > > org.apache.hadoop.fs.s3a.ITestS3AFileSystemIsolatedClassloader$CustomClassLoader@3e5ebdfe > > > with arguments [])* > > > > > > > > > > > > On Fri, Mar 27, 2026 at 12:03 PM Chris Nauroth <[email protected]> > > > wrote: > > > > > > > Are we sure about Java 21 client-side? This isn't something I've been > > > > specifically testing myself, and I don't think we have a CI run > > > configured > > > > with Java 21. > > > > > > > > I'm ~80% done with my test plan and expect to cast my vote soon. I've > > > found > > > > a few minor bugs to target for 3.5.1, but no blockers so far. > > > > > > > > Chris Nauroth > > > > > > > > > > > > On Fri, Mar 27, 2026 at 4:34 AM Steve Loughran <[email protected]> > > > > wrote: > > > > > > > > > +1 binding > > > > > > > > > > > > > > > 1. downloaded and validated binary tars using > > hadoop-release-support > > > > > (updated 3.5.0 properties with rc and staging info from the > email) > > > > > 2. maven build to validate dependencies > > > > > 3. local source build > > > > > 4. on arm64 linux box, download and validate native aarch64 > > > > artifacts, > > > > > including -native > > > > > 5. compared maven artifacts with those of x86 tar: they match > > > > > 6. added aws bundle.jar to binary release and attempted various > > > > > commands: all good > > > > > > > > > > No doubt there'll be surprises which need a followup, but we should > > > ship > > > > > this for java21 client support as well as java17 server. Then we > can > > > > handle > > > > > issues which are reported. Getting it out will mean that everyone > > who > > > > > wants a release with an updated jackson and other things has an > > > > actionable > > > > > answer "upgrade" rather than "wait". We get those emails on the > > > security > > > > > list. > > > > > > > > > > -steve > > > > > > > > > > > > > > > On Wed, 25 Mar 2026 at 13:02, Cheng Pan <[email protected]> wrote: > > > > > > > > > > > +1 (non-binding) > > > > > > > > > > > > 1. Passed Apache Spark integration tests[1] > > > > > > 2. Checked aarch64 binary tarball, content looks good, especially > > > > > > expected lz4-java 1.10.4 exists. > > > > > > 3. Deployed HDFS, YARN (with Spark External Shuffle Service Aux > > > > > > service) into a small cluster: > > > > > > i) 1 master, 3 workers, Ubuntu 24.04 arm64, OpenJDK 25, > Kerberos > > > > > > enabled, jsvc 1.5.1 > > > > > > ii) run some basic Spark jobs, randomly click YARN UI, > everything > > > > looks > > > > > > fine. > > > > > > > > > > > > [1] https://github.com/apache/spark/pull/54448 > > > > > > > > > > > > Thanks, > > > > > > Cheng Pan > > > > > > > > > > > > On Wed, Mar 25, 2026 at 1:03 PM Chris Nauroth < > [email protected] > > > > > > > > wrote: > > > > > > > > > > > > > > If you would like to use hadoop-release-support for > verification, > > > > > please > > > > > > > sync to the latest commit: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/hadoop-release-support/commit/27780bb09af7d9e85d5d7d94690b7ab369ee2cf3 > > > > > > > > > > > > > > Chris Nauroth > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 24, 2026 at 9:12 PM Chris Nauroth < > > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > > > I have put together a release candidate (RC2) for Hadoop > 3.5.0. > > > > > > > > > > > > > > > > This is a new minor version focused on JDK 17 compatibility, > > new > > > > > cloud > > > > > > > > storage integrations, dependency upgrades, security patches, > > and > > > > new > > > > > > > > features. > > > > > > > > > > > > > > > > Change log > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.5.0-RC2/CHANGELOG.md > > > > > > > > > > > > > > > > Release notes > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.5.0-RC2/RELEASENOTES.md > > > > > > > > > > > > > > > > The RC is available at: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.5.0-RC2/ > > > > > > > > > > > > > > > > The git tag is release-3.5.0-RC2, commit > > > > > > > > dbcc7cd797100e6b32cd84f85b53a5193a5f9af0. > > > > > > > > > > > > > > > > The maven artifacts are staged at > > > > > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehadoop-1470 > > > > > > > > > > > > > > > > You can find my public key at: > > > > > > > > > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS > > > > > > > > > > > > > > > > Please try the RC and vote. This vote is intended to run for > 5 > > > > days. > > > > > > > > > > > > > > > > Chris Nauroth > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > >
