Releases: Ayanda-D/rabbitmq-queue-master-balancer
Releases · Ayanda-D/rabbitmq-queue-master-balancer
v0.0.5
Release Notes
- This release ensures intermediate synchronisation checks are relative and proportional to the queue message depth. A new configuration is introduced,
sync_verification_factor
which applies verification check delays proportional to the queue depth of the current queue undergoing balance transition. This ensures resilient handling of queues bearing high message counts, and duration of queue balancing will ultimately take as (factorially) long the number of queue messages - #7 - The
policy_transition_delay
is also now relative to the queue message depth. When queues undergo balance, it will transition through different states, upon which it/they will be moved to nodes of least master queues to attain overall cluster equilibrium - #7 - Internal default
GenFSM
state event call timeouts have been bumped up to 30s #8 GenFSM
deprecation warnings have been turned off.GenStateM
version of the internal FSM remains on the roadmap #4 (until seen fitting to replace the currentGenFSM
core)- Build tools,
erlang.mk
andrabbitmq-components.mk
have been updated, thanks to Luke Bakken - #9 - The documentation has been updated to reflect message relative delay updates and more precise build and packaging instructions for both RabbitMQ
3.6.x
and3.7.x
releases
Release Packages (attached)
- The package compatible to RabbitMQ 3.7.x is
rabbitmq_queue_master_balancer-0.0.5.ez
. - The package compatible to RabbitMQ 3.6.x is
rabbitmq_queue_master_balancer-0.0.5___3.6.x.ez
. - Refer to the build instructions for more detail on building packages.
v0.0.4
- Transition policy timing delays caused referencing of queue master PIDs which had
terminated, e.g. following application or fallback of policies while queue state and
active PIDs in Mnesia were still set on old/terminated PID. This release introduces
resolution of this issue, as queue load and traffic pattern variations previously resulted
in intermittent transition cycle inconsistencies, resulting in queue incarnated PIDs
being made the primary entity of reference. - NOTE: This release is the first off v3.7.x branch. Previous releases have been off stable.
v0.0.3
- Significantly optimized FSM engine memory utilization
- Improved queue master capacity tolerance (e.g. to the order of hundreds of thousands, and millions)
- Introduction of FSM independent/non-service obstructing
rabbit_queue_master_balancer:status/0
call - API enhancements with user defined timeouts for
rabbit_queue_master_balancer:load_queues/1
rabbit_queue_master_balancer:info/1
rabbit_queue_master_balancer:report/1
calls during long running queue master balancing executions - Increased configuration settings for safe-guarded off-the shelf, default operation
v0.0.2
Support for RabbitMQ 3.7.x release series.