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
In a Khepri cluster if a node becomes partitioned, classic queues which get deleted due to the partition - do not get cancelled.
I am not sure if this is the intended behaviour - but in this case basically in a cluster no other than qq and streams are usable.
Reproduction steps
3 node cluster, enable khepri, RabbitMQ 4.0.2
Create a transient exclusive queue on each node and attach a consumer
Create a partition on one of the nodes (full partition, but expect the same happens in case of a partial partition)
The node becomes partitioned
a. Queue gets deleted on majority partition
b. Queue stays running on minority partition
Remove the partition
Minority node syncs with khepri, queue disappears
No notification to the consumer on minority node that the queue no longer exists
Expected behavior
Any or all of the following: :-)
a. Client gets notified about the queue deletion
b. Queue is not deleted as the consumer was not disconnected
c. Something akin to pause_minority
d. Clarification of the intended use of transient exclusive queues in a cluster
e. Specified behaviour in case of partial partition as well
Additional context
The queue process is still running, even though the queue is deleted from khepri. (which is understandable, I am just noting it here).
The text was updated successfully, but these errors were encountered:
michaelklishin
changed the title
Transient exclusive queues with Khepri do not get cancelled in case of partition
With Khepri, transient exclusive queues are not deleted in case of a partition
Oct 28, 2024
Describe the bug
Hi,
In a Khepri cluster if a node becomes partitioned, classic queues which get deleted due to the partition - do not get cancelled.
I am not sure if this is the intended behaviour - but in this case basically in a cluster no other than qq and streams are usable.
Reproduction steps
running
on minority partitionExpected behavior
Any or all of the following: :-)
a. Client gets notified about the queue deletion
b. Queue is not deleted as the consumer was not disconnected
c. Something akin to pause_minority
d. Clarification of the intended use of transient exclusive queues in a cluster
e. Specified behaviour in case of partial partition as well
Additional context
The text was updated successfully, but these errors were encountered: