+1 I forgot to mention I built , verified sigs and hashes this weekend.
Deployed jars as a replacement of a pre rc cluster of a multi TB graph with three tsevers. It's still running and ingesting data without any failures in scans or compactors. Great work and thanks Christopher for the reminder! On Wed, Sep 23, 2026, 8:23 PM Christopher <[email protected]> wrote: > +1 (binding) > > - verified signatures and hashes of all staged artifacts > - verified 3 expected tarballs (source, binary, and native lib) > - jars have corresponding javadoc/source jars > - jars are sealed > - manifest in jars matches git commit > - jars in binary tarball are same as staged in maven > - tarball SHA512s match email > - branch matches git commit > - git commit contains same content as source tarball > - verified `mvn clean verify -Psunny` with Maven 3.9 and JDK 21 > > Some small non-blocker issues: > > - license plugin and rat plugin excludes were not updated when > resources were moved in #6444 (rat seems fine with it, but license > emits warnings) > - the LICENSE files for the monitor jar and the assemble tarball > reference for DataTables buttons and colreaorder libraries refer to > server/monitor/ for the source path, rather than the path to the > monitor jar in the binary distribution; those source paths don't exist > in the binary distribution, so they should be updated to be consistent > with the other entries; problem was introduced in #6392 > > On Wed, Sep 23, 2026 at 12:22 PM Dominic Garguilo > <[email protected]> wrote: > > > > +1 (binding) > > > > - Verified the git branch 4.0.0-alpha-1-rc1 points to the mentioned > > commit 720bdd19537d2d8fc5c403a25d28d5cff474924b > > - Verified the GPG signatures for source and binary tarballs > > - Verified SHA1 and MD5 hashes for source and binary tarballs > > - Checked LICENSE, NOTICE, and README in source and binary tarballs > > - Verified no unexpected binary artifacts in source tarball > > - Successfully ran `mvn clean verify -Psunny` from source > > - Stood up a local 5 node cluster with 3 managers, 5 tservers, 5 scan > > servers, and 35 compactors across small/medium/large resource groups > > - Built and ran accumulo testing against the staged artifacts: ran > > continuous ingest and verify passed at ~2.5B entries > > - Verified distributed FATE across 3 managers > > - Tested manager failover by killing the primary, recovered in 35s > > - Ran accumulo-testing agitator during ingest for ~2.5 hrs killing > > managers, tservers, and datanodes. All recovered. > > > > Found something that doesn't affect correctness: > > - https://github.com/apache/accumulo/pull/6557 fate workers poll the > > work queue every 1ms so idle managers burn 24-95% of a core doing > > nothing. > > > > On Fri, Sep 18, 2026 at 1:47 PM Dave Marion <[email protected]> wrote: > > > > > > +1 (binding) > > > > > > I performed the following checks: > > > > > > Validated signature and hashes > > > Verified no unexpected binary files in source release artifact > > > Confirmed source tarball builds, sunny tests pass > > > Verified LICENSE and NOTICE files > > > Cluster testing: > > > Created a 4-node cluster > > > Loaded over 2B entries into the ci table > > > Ran verify (succeeded), walk, batchwalk > > > Testing merge and split behavior > > > Confirmed Monitor matched cluster activity > > > > > > I created the following issues, none of which I think are blockers for > this > > > alpha tag. > > > #6539, #6540, #6542, #6543, #6544, #6545, #6546, #6547 > > > > > > On Wed, Sep 16, 2026 at 12:46 PM Dave Marion <[email protected]> > wrote: > > > > > > > Accumulo Developers, > > > > > > > > Please consider the following candidate for Apache Accumulo > 4.0.0-alpha-1. > > > > > > > > Git Commit: > > > > 720bdd19537d2d8fc5c403a25d28d5cff474924b > > > > Branch: > > > > 4.0.0-alpha-1-rc1 > > > > > > > > If this vote passes, a gpg-signed tag will be created using: > > > > git tag -f -s -m 'Apache Accumulo 4.0.0-alpha-1' \ > > > > rel/4.0.0-alpha-1 \ > > > > 720bdd19537d2d8fc5c403a25d28d5cff474924b > > > > > > > > Staging repo: > > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1127 > > > > Source (official release artifact): > > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1127/org/apache/accumulo/accumulo/4.0.0-alpha-1/accumulo-4.0.0-alpha-1-src.tar.gz > > > > Binary: > > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1127/org/apache/accumulo/accumulo/4.0.0-alpha-1/accumulo-4.0.0-alpha-1-bin.tar.gz > > > > > > > > Append ".asc" to download the cryptographic signature for a given > artifact. > > > > (You can also append ".sha1" or ".md5" instead in order to verify the > > > > checksums > > > > generated by Maven to verify the integrity of the Nexus repository > staging > > > > area.) > > > > > > > > Signing keys are available at > https://www.apache.org/dist/accumulo/KEYS > > > > (Expected fingerprint: CF4A5B6E1321844EB658728306CC9CA1F9BF248E) > > > > > > > > In addition to the tarballs and their signatures, the following > checksum > > > > files will be added to the dist/release SVN area after release: > > > > accumulo-4.0.0-alpha-1-src.tar.gz.sha512 will contain: > > > > SHA512 (accumulo-4.0.0-alpha-1-src.tar.gz) = > > > > > e510eda1533655055cc8f2b9d691da13a38777b4999a9c9b155e97a8aa8a9adc319530df24e610fc9caa4b87bbbb27faae3c4d2e524c88cd93481c5d81524d1f > > > > accumulo-4.0.0-alpha-1-bin.tar.gz.sha512 will contain: > > > > SHA512 (accumulo-4.0.0-alpha-1-bin.tar.gz) = > > > > > b28187c4fae62b76b1da2e3cf3195316d99d4a27628e3ba5c69f31b0747e9e28d1e469710c68ba1aeb3c6a041364f9b23006302a64f6a6d26f09ce14c23c472a > > > > > > > > Release notes (in progress) can be found at: > > > > https://accumulo.apache.org/release/accumulo-4.0.0-alpha1 > > > > > > > > Issues and pull requests related to this release can be found at: > > > > > https://github.com/apache/accumulo/issues?q=state%3Aclosed+milestone%3A4.0.0 > > > > > > > > Release testing instructions: > > > > https://accumulo.apache.org/contributor/verifying-release > > > > > > > > Please vote one of: > > > > [ ] +1 - I have verified and accept... > > > > [ ] +0 - I have reservations, but not strong enough to vote > against... > > > > [ ] -1 - Because..., I do not accept... > > > > ... these artifacts as the 4.0.0-alpha-1 release of Apache Accumulo. > > > > > > > > This vote will remain open until at least Sat Sep 19 17:00:00 UTC > 2026. > > > > (Sat Sep 19 13:00:00 EDT 2026 / Sat Sep 19 10:00:00 PDT 2026) > > > > Voting can continue after this deadline until the release manager > > > > sends an email ending the vote. > > > > > > > > Thanks! > > > > > > > > P.S. Hint: download the whole staging repo with > > > > wget -erobots=off -r -l inf -np -nH \ > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1127/ > > > > # note the trailing slash is needed > > > > >
