OpenStack RabbitMQ Server Charm

  1. Bug #1768986
  2. Comment #7

Comment 7 for bug 1768986

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-rabbitmq-server (stable/jammy)

Reviewed: https://review.opendev.org/c/openstack/charm-rabbitmq-server/+/880172
Committed: https://opendev.org/openstack/charm-rabbitmq-server/commit/552eb3a5d212d6121a894bd36b5f58870e18b92d
Submitter: "Zuul (22348)"
Branch: stable/jammy

commit 552eb3a5d212d6121a894bd36b5f58870e18b92d
Author: Vern Hart <email address hidden>
Date: Thu May 3 21:46:22 2018 +0000

    Enforce a maximum of 1024 async threads.

    The beam.smp process won't start if more than 1024 are configured, the
    charm could make this by default on large systems (e.g. more than 42
    CPUs). This change makes RabbitMQEnvContext.calculate_threads() never
    return more than 1024 (MAX_NUM_THREADS).

    Change-Id: I92879445210bac6ee7d96a704cdf428ca738e3b6
    Closes-Bug: #1768986
    (cherry picked from commit 3c1c05ee598b2fc85ddf0f971528dde433312bff)