Hermes v1.3.0 Release Notes
-
๐ Features
(1110) Flat binary storage for consumers workload
๐ Introducing more concise registry type for consumers workload distribution that should help scale better. Each consumer uses a single znode that contains binary encoded list of subscriptions that the consumer should process. โก๏ธ The configuration loads fast and is updated only on workload distribution change. 0๏ธโฃ Enabled with
consumer.workload.registry.type=flat-binary
setting. The default ishierarchical
type.A single consumer registry and leader election
๐ท Consumer registry is extracted from consumer workload and is now used by max-rate job as well. The registry contains a leader latch which is always enabled and available.
๐ (1095) Removal of deprecated
StrictMaxRateProvider
๐ The legacy max-rate provider type is now removed.
Removal of inflight message counter
๐ The inflight message counter as well as the distributed zookeeper counter are now removed. This feature was not used but was leaving a lot of junk in zookeeper.
(1106) Consumer constraints management in hermes-console
This feature allows easy management of consumer constraints. Link to it is not visible in the home screen as it is an admin feature (all endpoints are admin-secured though), accessed from
http://<hermes-console>/#/constraints
URL.(1113) Frontends wait for kafka when booting up
๐ Frontends will not start the HTTP server unless the underlying kafka brokers are available, i.e. we can fetch topics metadata from them. 0๏ธโฃ By default the feature is disabled, enable with
frontend.startup.wait.kafka.enabled=true
.(1109) Cancel all waiting messages on stopping sender
When a subscription is stopped all messages that were already accepted by consumer message sender will be now dropped.