Mohit20057 commented on PR #9168:
URL: https://github.com/apache/storm/pull/9168#issuecomment-6337571466
Hi @rzo1 @reiabreu,
Thanks for the review! I have added a `LOG.warn(...)` in `Nimbus` when a
submitted topology specifies `topology.backpressure.enable`. Here is the
Release & Upgrade Note for this PR:
### Release & Upgrade Note: Removal of Legacy ZooKeeper Backpressure State
1. **Removal of `Config.TOPOLOGY_BACKPRESSURE_ENABLE`**:
- The public constant `Config.TOPOLOGY_BACKPRESSURE_ENABLE`
(`"topology.backpressure.enable"`), originally marked for removal in 2.0.0, has
been removed.
- Worker backpressure in modern Storm versions is automatically handled
in-process via internal worker queues/buffering; the legacy
ZooKeeper-coordinated backpressure toggle is obsolete. Topologies submitting
this key will now receive a log warning.
2. **ZooKeeper `/backpressure` Znodes Cleanup Notice**:
- The legacy cluster-state methods (`backpressure()`,
`setupBackpressure()`, `removeBackpressureFlag()`, etc.) and the associated
cleanup routine in Nimbus have been removed.
- **Notice for Cluster Operators**: Clusters upgraded from legacy 1.x
installations (or topologies that previously used ZooKeeper-based backpressure)
will no longer have lingering `/backpressure` znodes automatically purged by
Nimbus. Operators can safely delete any orphaned historical znodes directly in
ZooKeeper using the zkCli tool (`rmr /storm/backpressure` or `deleteall
/storm/backpressure`).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
