+1
Actions taken:
1. Signatures and checksums
- Downloaded all 21 files of ATR revision 00002 (src, full and lite
binaries, tar.gz and zip each, release notes).
- All 7 GPG signatures are good, made by Rui's key.
- All 7 SHA512 checksums OK; all 21 files match the SHA3-256 digests in
the ATR manifest.
2. Archive contents
- Source tarball compared with the v3.2.0 tag (98ce70603): no content
differences. Same leftovers as in 3.1.0: dependency-reduced-pom.xml
in 15 modules and an empty storm-server/csvmetrics/ directory.
Harmless.
- src zip and tar.gz have identical file lists; same for the full and
lite binary zip/tar.gz pairs.
- Lite = full minus external/storm-autocreds (108 files) and
lib-tools/storm-kafka-monitor (40 files), nothing else.
3. Build
- mvn clean install -DskipTests on the source tarball: BUILD SUCCESS.
4. Distributed cluster from the binaries
- Built two Docker images, one from apache-storm-3.2.0.tar.gz (full)
and one from apache-storm-3.2.0-lite.tar.gz.
- Cluster: ZooKeeper, Nimbus, two supervisors on separate containers,
UI. Every topology ran with 2 workers, one per supervisor, so tuples
crossed the network.
- storm version reports Storm 3.2.0, Branch v3.2.0.
5. storm-perf topologies (jar built from the RC source), on both full
and lite. These complement the storm-starter and Kafka runs already
reported in this thread. Acked/failed numbers come from the UI REST
API, just before each topology was killed:
- ConstSpoutIdBoltNullBoltTopo (acking on, 2 ackers), 5 min:
about 8.1M tuples acked, complete latency about 6 ms. A few sampled
failures (well under 0.1%). Lite ran the same topology without
problems; throughput varied between runs on my laptop-hosted
cluster.
- FileReadWordCountTopo with
topology.tuple.deserialization.strict.enable=true (#9094/#9159):
about 4.95M tuples acked in under 2 min, 0 failed (full). No
deserialization errors in the worker logs (full and lite).
6. Virtual threads (#9097)
- Full image with storm.virtual.threads.enabled=true on Nimbus and
both supervisors (it switches the Thrift server handler pools).
- Jar upload, submission, storm list and all UI/metrics Thrift calls
work. ConstSpoutIdBoltNullBoltTopo: about 20.5M tuples acked,
0 failed, complete latency about 6.3 ms.
7. Logs
- No unexpected ERRORs in daemon or worker logs. Only Netty
connection retries at worker start-up and "Dropping messages ...
client is being closed" at topology kill, both as in earlier
releases.
Thanks Rui for driving the release!
Gianluca
On 2026-11-07 23:33 UTC rabreu.apache.org via dev wrote:
> Hello Storm,
>
> I'd like to call a vote on releasing the following artifacts as
> Apache Storm 3.2.0. This vote is being conducted using a
> Beta version of the Apache Trusted Releases (ATR) platform.
> Please report any bugs or issues to the ASF Tooling team.
>
> The page of the release candidate from ATR revision 00002,
> which includes downloads and the release notes, can be found at:
>
> https://releases.apache.org/vote/storm/3.2.0
>
> The file manifest for ATR revision 00002, including file digests,
> can be found at:
>
> https://releases.apache.org/manifest/storm/3.2.0/00002
>
> The release artifacts are signed with one or more OpenPGP keys from:
>
> https://downloads.apache.org/storm/KEYS
>
> The release was made from the Apache Storm 3.2.0 tag, commit
> 98ce70603d9f7fa28725c5cf41af92ebea9a38b1:
>
> https://github.com/apache/storm/tree/v3.2.0
>
> The Nexus staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1131
>
> To use it in a maven build, set the version for Storm to 3.2.0 and add
> that URL to your settings.xml file.
>
> The binary release comes in two flavours: the full distribution and the lite
> distribution (apache-storm-3.2.0-lite.*), which omits the storm-autocreds
> and storm-kafka-monitor jars. Please verify both, and the source release.
>
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> When voting, please list the actions taken to verify the release.
>
> Please review the release candidate and vote accordingly.
>
> [ ] +1 Release this package
> [ ] +0 Abstain
> [ ] -1 Do not release this package (please provide specific comments)
>
> You can vote on ATR at the URL above, or manually by replying to this email.
>
> The vote is open for 72 hours. Only votes from the Storm PMC are
> binding, but everyone is welcome to vote. The vote passes with at least three
> binding +1 votes.
>
> Thanks,
> Rui Abreu (rabreu)
>
> This email was sent by [email protected] on the Apache Trusted Releases
> platform
>
