Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decrease default MQTT mailbox_soft_limit #7234

Merged
merged 2 commits into from
Feb 9, 2023
Merged

Decrease default MQTT mailbox_soft_limit #7234

merged 2 commits into from
Feb 9, 2023

Commits on Feb 9, 2023

  1. Decrease MQTT mailbox_soft_limit 

    Let's decrease the mailbox_soft_limit from 1000 to 200.
Obviously, both values are a bit arbitrary.
However, MQTT workloads usually do not have high throughput patterns for
a single MQTT connection. The only valid scenario where an MQTT
connections' process mailbox could have many messages is in large fan-in
scenarios where many MQTT devices sending messages at once to a single MQTT
device - which is rather unusual.

It makes more sense to protect against cluster wide memory alarms by
decreasing the mailbox_soft_limit.
    @ansd
    ansd committed Feb 9, 2023
    Configuration menu
    Copy the full SHA
    9bb1f7a View commit details
    Browse the repository at this point in the history

  2. Add test that MQTT ingores configured default queue type 

    The queue type being created for MQTT connections is solely determined
by the rabbitmq_mqtt plugin, not by per vhost defaults.

If the per vhost default queue type is configured to be a quorum queue,
we still want to create classic queues for MQTT connections.
    @ansd
    ansd committed Feb 9, 2023
    Configuration menu
    Copy the full SHA
    56e78cd View commit details
    Browse the repository at this point in the history