Define unique hostname for QManager
Due to the shortcoming of QManager implementation [1], in case of uWSGI usage on metal hosts, the flow ends up with having the same hostname/processname set, making services to fight over same file under SHM. In order to avoid this, we prepend the hostname with a service_name. We can not change processname instead, since it will lead to the fight between different processes of the same service. [1] https://bugs.launchpad.net/oslo.messaging/+bug/2065922 Change-Id: I0c310abd4c2144a068e75aaea665befeee0a5ff6
This commit is contained in:
parent
e712535365
commit
bedc003fb2
@ -59,6 +59,9 @@ rabbit_quorum_queue = {{ manila_oslomsg_rabbit_quorum_queues }}
|
||||
rabbit_transient_quorum_queue = {{ manila_oslomsg_rabbit_transient_quorum_queues }}
|
||||
rabbit_qos_prefetch_count = {{ manila_oslomsg_rabbit_qos_prefetch_count }}
|
||||
use_queue_manager = {{ manila_oslomsg_rabbit_queue_manager }}
|
||||
{% if manila_oslomsg_rabbit_queue_manager %}
|
||||
hostname = {{ [ansible_facts['hostname'], manila_service_name] | join('-') }}
|
||||
{% endif %}
|
||||
rabbit_stream_fanout = {{ manila_oslomsg_rabbit_stream_fanout }}
|
||||
rabbit_quorum_delivery_limit = {{ manila_oslomsg_rabbit_quorum_delivery_limit }}
|
||||
rabbit_quorum_max_memory_bytes = {{ manila_oslomsg_rabbit_quorum_max_memory_bytes }}
|
||||
|
Loading…
Reference in New Issue
Block a user