Thanks a lot Mukund!
+1 (non-binding) * Verified sha512 checksum was correct for source tarball * Verified signature was correct for source tarball (not verified trust) * Built source code on Amazon-Linux 2 and OpenJDK 8 in Amazon EC2 * Verified S3A (hadoop-tools/hadoop-aws) unit tests passing * Verified S3A (hadoop-tools/hadoop-aws) integ tests with scale profile passing against Amazon S3 in eu-west-1 ________________________________ From: Mukund Madhav Thakur <mtha...@cloudera.com.INVALID> Sent: Thursday, October 10, 2024 12:17:34 PM To: Hadoop Common Subject: [EXTERNAL] [VOTE] Release Apache Hadoop 3.4.1 RC3 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Apache Hadoop 3.4.1 With help of Steve, I have put together a release candidate (RC3) for Hadoop 3.4.1. 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://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.4.1-RC3/ The git tag is release-3.4.1-RC3, commit 4d7825309348956336b8f06a08322b78422849b1 The maven artifacts are staged at https://repository.apache.org/content/repositories/orgapachehadoop-1430 You can find my public key at: https://dist.apache.org/repos/dist/release/hadoop/common/KEYS Change log https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.4.1-RC3/CHANGELOG.md Release notes https://dist.apache.org/repos/dist/dev/hadoop/hadoop-3.4.1-RC3/RELEASENOTES.md This is off branch-3.4.1 Key changes include * Bulk Delete API. https://issues.apache.org/jira/browse/HADOOP-18679 * Fixes and enhancements in Vectored IO API. * Improvements in Hadoop Azure connector. * Fixes and improvements post upgrade to AWS V2 SDK in S3AConnector. * This release includes Arm64 binaries. Please can anyone with compatible systems validate these. 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 source tarballs, the binaries are there for help only, though with the maven repo that's a bit blurred). The only way to be consistent would actually untar the x86.tar.gz, overwrite its binaries with the arm stuff, retar, sign and push out for the vote. Even automating that would be risky. Please try the release and vote. The vote will run for 5 days.
