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: Icb9df1114b6fda8509fb12aeac486ca52e370781
This commit is contained in:
parent
8d62100e61
commit
da852f307f
@ -108,6 +108,9 @@ rabbit_quorum_queue = {{ zun_oslomsg_rabbit_quorum_queues }}
|
||||
rabbit_transient_quorum_queue = {{ zun_oslomsg_rabbit_transient_quorum_queues }}
|
||||
rabbit_qos_prefetch_count = {{ zun_oslomsg_rabbit_qos_prefetch_count }}
|
||||
use_queue_manager = {{ zun_oslomsg_rabbit_queue_manager }}
|
||||
{% if zun_oslomsg_rabbit_queue_manager %}
|
||||
hostname = {{ [ansible_facts['hostname'], zun_service_name] | join('-') }}
|
||||
{% endif %}
|
||||
rabbit_stream_fanout = {{ zun_oslomsg_rabbit_stream_fanout }}
|
||||
rabbit_quorum_delivery_limit = {{ zun_oslomsg_rabbit_quorum_delivery_limit }}
|
||||
rabbit_quorum_max_memory_bytes = {{ zun_oslomsg_rabbit_quorum_max_memory_bytes }}
|
||||
|
Loading…
Reference in New Issue
Block a user