Bug 1150710 - no rabbitmq.config file
Summary: no rabbitmq.config file
Keywords:
Status: CLOSED DUPLICATE of bug 1134956
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 5.0 (RHEL 6)
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: John Eckersberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-08 18:47 UTC by Dan Yocum
Modified: 2016-04-18 06:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-08 19:21:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
new and improved rabbitmq.config file (9.61 KB, text/x-matlab)
2014-10-08 19:15 UTC, Dan Yocum
no flags Details

Description Dan Yocum 2014-10-08 18:47:06 UTC
Description of problem:

There is no /etc/rabbitmq.config file in /etc/rabbitmq/.  This should exist, and contain reasonable defaults for a cloud with 67 system OpenStack cloud (64 compute nodes, 3 controllers).

Version-Release number of selected component (if applicable):

3.1.5-6.0.el6ost

A *suggested* config file is attached.

NB: I will test this in the OS1 Internal cloud soon and update this ticket with my findings.

Comment 2 Dan Yocum 2014-10-08 19:15:44 UTC
Created attachment 945135 [details]
new and improved rabbitmq.config file

This one works, and these are the settings, so far (not literally - see the attached file which is erlang compliant):

vm_memory_high_watermark=0.4 #default to start
vm_memory_high_watermark_paging_ratio=0.5 #default to start
disk_free_limit=50000000 #default to start
log_levels=[{connection, info, mirroring}]
frame_max=131072 #default to start
channel_max=128 #default to start
heartbeat=600 #default to start
cluster_nodes={[],disk} #default, could be disk or ram
server_properties=[]
auth_mechanisms=['PLAIN', 'AMQPLAIN'] #default
delegate_count=16 #default
hipe_compile=true #slow startup (1 min), 20-50% performance increase

Comment 3 John Eckersberg 2014-10-08 19:21:22 UTC

*** This bug has been marked as a duplicate of bug 1134956 ***


Note You need to log in before you can comment on or make changes to this bug.