Is There any possiblilty to publish message to queue with specific consumer using consumer tag

[akk017]

Community Support Policy

• I have read RabbitMQ's Community Support Policy
• I run RabbitMQ 4.x, the only series currently covered by community support
• I promise to provide all relevant information (versions, logs from all nodes, rabbitmq-diagnostics output, detailed reproduction steps)

RabbitMQ version used

4.1.1

Erlang version used

26.0.x

Operating system (distribution) used

Debian

How is RabbitMQ deployed?

Generic binary package

rabbitmq-diagnostics status output

See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics

# PASTE OUTPUT HERE, BETWEEN BACKTICKS

Logs from node 1 (with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 2 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 3 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

rabbitmq.conf

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location

# PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS

Steps to deploy RabbitMQ cluster

Our RabbitMQ runs debian12 and debain 11 machines. we in our company use internal tool to automate deployment. deployment can be configured based on the component requirements.

Steps to reproduce the behavior in question

Any Default RabbitMQ Configs would do

advanced.config

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location

# PASTE advanced.config HERE, BETWEEN BACKTICKS

Application code

# PASTE CODE HERE, BETWEEN BACKTICKS

Kubernetes deployment file

# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS

What problem are you trying to solve?

publish to queue using "x-consumer-tag" header, this header may possibly point to specific consumer if found give message to that consumer or default way

[michaelklishin]

There isn't. Publishers should not be consumer-aware.

There's a way to have only one active consumer on a queue or stream.

[akk017]

Why should publisher not know about consumer.

[akk017]

"x-consumer-tag" is not going to be mandatory header, its a preference, that this consumer is most suitable and scheduling like thing could be achieved.
routing logic could be handled by client if needed.

[michaelklishin]

@akk017 because of coupling.

Besides the SAC, every consumer can use a dedicated, well-known queue name, or a server-named queue whose name it can pass around (see tutorial 6).

There is absolutely no need to "route to a consumer", and every protocol RabbitMQ supports has the concept of a destination (an exchange, a topic, a destination) that is not a consumer, and, in the case of AMQP 0-9-1, is very explicitly not a "consumer" by design.

[michaelklishin]

routing logic could be handled by client if needed

Yeah, right. Let's turn every protocol and abstraction we have upside down over something that's entirely unnecessary. In particular when you won't spend any time implementing or maintaining such a feature forever.

Use a queue per consumer or the SAC, or both.