spring-cloud / spring-cloud/spring-cloud-stream
RabbitMQ: Ensure Binding has a Group When Using a Quorum Queue
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
From Slack discussion:
--spring.cloud.stream.rabbit.bindings.input.consumer.quorum.enabled=true
2023-10-27 09:54:23.139267-04:00 [error] <0.24240.0> operation queue.declare caused a channel exception not_found: no queue 'jdbc-sink.anonymous.fLej1aQ0RZuKeliKqFZnjw' in vhost '/'
You cannot create auto delete (anonymous) quorum queues.
We should detect the condition and require a group.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the RabbitMQ binding consumer configuration, especially the quorum.enabled property shown in the issue, and reproduce the anonymous quorum-queue failure. Trace how a binding without a group is handled; done means the condition is detected and a group is required instead of attempting to create an auto-delete quorum queue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, rabbitmq, spring
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100