Skip to content

Quorum queue declaration behavior when initial replica count < actual cluster member at declaration time #3850

Closed
@rubber-ant

Description

@rubber-ant

Issue discussed with @mkuratczyk on slack: https://rabbitmq.slack.com/archives/CTMSV81HA/p1638543089101700

Example issue: a cluster with 3 nodes and quorum queue have only 1 member instead of 3 at

image

image

Scenario:

this happens when a queue is declared by a consumer/producer pod running before the initial rabbitmq cluster starts.
Once the cluster start rabbitmq-0 all the quorum queues stick with only 1 members=rabbitmq-0 and once the node rabbitmq-1 and rabbitmq-2 are up too and the nodes are part of the cluster, they are ignored by the quorum queues unless I manually delete the queues or run rabbitmq-queues add_member for each queue

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy