You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much like quorum queues, streams generally assume that the (human) operator is explicit about replica management.
Over time, rabbitmq-queues add_replica was largely replaced by rabbitmq-queues grow, which
operates on groups of queues, and is more useful during automation.
However, there is no rabbitmq-streams grow, an equivalent for streams. This is because streams were not designed for environments where replicas dynamically change often enough to warrant such a command. But we can at least consider it one more time.
The text was updated successfully, but these errors were encountered:
There's been some opposition to dynamically managing stream replicas. We may revisit this at some point but right now it looks like this issue won't be considered or tackled in the foreseeable future.
Much like quorum queues, streams generally assume that the (human) operator is explicit about replica management.
Over time,
rabbitmq-queues add_replica
was largely replaced byrabbitmq-queues grow
, whichoperates on groups of queues, and is more useful during automation.
However, there is no
rabbitmq-streams grow
, an equivalent for streams. This is because streams were not designed for environments where replicas dynamically change often enough to warrant such a command. But we can at least consider it one more time.The text was updated successfully, but these errors were encountered: