[Questions] - How to Enable QoS 1 in RabbitMQ Server for the MQTT Plugin with Quorum Queues

[iamhritik]

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.0.3

Erlang version used

26.2.x

Operating system (distribution) used

Ubuntu 22.04.5 LTS

How is RabbitMQ deployed?

Debian package

rabbitmq-diagnostics status output

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

Runtime

OS PID: 9082
OS: Linux
Uptime (seconds): 1550561
Is under maintenance?: false
RabbitMQ version: 3.13.3
RabbitMQ release series support status: supported
Node name: rabbit@nonprod-rabbitmq-3
Erlang configuration: Erlang/OTP 26 [erts-14.2.5.3] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [jit]
Crypto library: OpenSSL 3.0.2 15 Mar 2022
Erlang processes: 524 used, 1048576 limit
Scheduler run queue: 1
Cluster heartbeat timeout (net_ticktime): 60

Plugins

Enabled plugin file: /etc/rabbitmq/enabled_plugins
Enabled plugins:

 * rabbitmq_prometheus
 * rabbitmq_shovel_management
 * rabbitmq_federation
 * rabbitmq_sharding
 * rabbitmq_peer_discovery_aws
 * rabbitmq_consistent_hash_exchange
 * accept
 * rabbitmq_peer_discovery_common
 * rabbitmq_random_exchange
 * rabbitmq_shovel
 * amqp10_client
 * prometheus
 * rabbitmq_aws
 * rabbitmq_web_mqtt
 * rabbitmq_mqtt
 * rabbitmq_management
 * rabbitmq_management_agent
 * rabbitmq_web_dispatch
 * amqp_client
 * cowboy
 * cowlib
 * oauth2_client
 * jose

Data directory

Node data directory: /var/lib/rabbitmq/mnesia/rabbit@nonprod-rabbitmq-3
Raft data directory: /var/lib/rabbitmq/mnesia/rabbit@nonprod-rabbitmq-3/quorum/rabbit@nonprod-rabbitmq-3

Config files

 * /etc/rabbitmq/rabbitmq.conf

Log file(s)

 * /var/log/rabbitmq/rabbit@nonprod-rabbitmq-3.log
 * <stdout>

Alarms

(none)

Memory

Total memory used: 0.1584 gb
Calculation strategy: rss
Memory high watermark setting: 0.9 of available memory, computed to: 3.6186 gb

reserved_unallocated: 0.0811 gb (51.22 %)
code: 0.0369 gb (23.32 %)
other_system: 0.0237 gb (14.97 %)
other_proc: 0.0193 gb (12.2 %)
other_ets: 0.004 gb (2.55 %)
plugins: 0.0025 gb (1.59 %)
atom: 0.0019 gb (1.18 %)
binary: 0.0012 gb (0.78 %)
quorum_queue_procs: 0.0009 gb (0.55 %)
metrics: 0.0006 gb (0.36 %)
mgmt_db: 0.0003 gb (0.19 %)
msg_index: 0.0003 gb (0.16 %)
quorum_ets: 0.0002 gb (0.1 %)
mnesia: 0.0001 gb (0.09 %)
metadata_store: 0.0001 gb (0.09 %)
metadata_store_ets: 0.0 gb (0.02 %)
connection_other: 0.0 gb (0.0 %)
quorum_queue_dlx_procs: 0.0 gb (0.0 %)
stream_queue_procs: 0.0 gb (0.0 %)
stream_queue_replica_reader_procs: 0.0 gb (0.0 %)
connection_readers: 0.0 gb (0.0 %)
connection_writers: 0.0 gb (0.0 %)
connection_channels: 0.0 gb (0.0 %)
queue_procs: 0.0 gb (0.0 %)
queue_slave_procs: 0.0 gb (0.0 %)
stream_queue_coordinator_procs: 0.0 gb (0.0 %)
allocated_unused: 0.0 gb (0.0 %)

File Descriptors

Total: 16, limit: 75439
Sockets: 0, limit: 67893

Free Disk Space

Low free disk space watermark: 0.05 gb
Free disk space: 19.643 gb

Totals

Connection count: 0
Queue count: 8
Virtual host count: 2

Listeners

Interface: 0.0.0.0, port: 15672, protocol: http, purpose: HTTP API
Interface: 0.0.0.0, port: 1443, protocol: mqtt, purpose: MQTT
Interface: [::], port: 15675, protocol: http/web-mqtt, purpose: MQTT over WebSockets
Interface: [::], port: 15692, protocol: http/prometheus, purpose: Prometheus exporter API over HTTP
Interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication
Interface: 0.0.0.0, port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0

Logs from node 1 (with sensitive values edited out)

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

N/A

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

listeners.tcp.1 = 0.0.0.0:5672
mqtt.listeners.tcp.1 = 0.0.0.0:1443
mqtt.tcp_listen_options.backlog = 9182
mqtt.tcp_listen_options.recbuf  = 191072
mqtt.tcp_listen_options.sndbuf  = 191072
mqtt.tcp_listen_options.keepalive = true
mqtt.tcp_listen_options.nodelay   = true
mqtt.tcp_listen_options.exit_on_close = true
mqtt.tcp_listen_options.send_timeout  = 120
# anonymous connections, if allowed, will use the default
# credentials specified here
mqtt.allow_anonymous  = false
mqtt.default_user     = guest
mqtt.default_pass     = guest
mqtt.vhost            = /
mqtt.exchange         = amq.topic
# 24 hours by default
mqtt.max_session_expiry_interval_seconds = 86400
#mqtt.prefetch         = 10
management.listener.port = 15672
management.listener.ip   = 0.0.0.0

###### Disk & Memory Configuration ######
disk_free_limit.absolute = 50MB
vm_memory_high_watermark.relative = 0.9

## web_mqtt
web_mqtt.tcp.port      = 15675
######## Logging #######
log.file.level = info
log.file.formatter = json

handshake_timeout = 20000
tcp_listen_options.backlog = 9182
tcp_listen_options.recbuf  = 191072
tcp_listen_options.sndbuf  = 191072
tcp_listen_options.keepalive = true
tcp_listen_options.nodelay   = true

Steps to deploy RabbitMQ cluster

Deployed Rabbitmq cluster on AWS EC2 Nodes

Steps to reproduce the behavior in question

Simply setup rabbitmq-server cluster on aws ec2 nodes using the below rabbitmq conf

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?

We need to send messages from the Application using Paho MQTT client to the RabbitMQ server with QoS 1 using the MQTT protocol. Do we need to make any changes to the RabbitMQ server configuration? In our current setup, we are using a quorum queue with the amq.topic exchange and specific binding keys

[ansd]

No RabbitMQ server configuration changes are needed in your use case.

You only need to change server configuration if the MQTT plugin should create quorum queues for your MQTT subscribers: https://www.rabbitmq.com/docs/mqtt#quorum-queues