Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1255091

Summary: Overcloud: RabbitMQ file-descriptor limit configuration
Product: Red Hat OpenStack Reporter: Udi Shkalim <ushkalim>
Component: rhosp-directorAssignee: chris alfonso <calfonso>
Status: CLOSED DUPLICATE QA Contact: Udi Shkalim <ushkalim>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: hbrock, jeckersb, jslagle, mburns, rhel-osp-director-maint
Target Milestone: z1Keywords: ZStream
Target Release: Director   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-19 21:02:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Udi Shkalim 2015-08-19 15:01:19 UTC
Description of problem:
Currently the default configuration for FD limit in rabbitmq is 1024 which causing performance and HA issues. Need to increase the default limit.

Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-3.el7ost.noarch
openstack-puppet-modules-2015.1.8-8.el7ost.noarch
2015.1.0

How reproducible:
100%

Steps to Reproduce:
1. Deploy HA setup 
2. Go to one of the controllers and run the command: rabbitmqctl status and search for the file_descriptors section
3.

Actual results:
1024

Expected results:
16384

Additional info:
[root@overcloud-controller-0 ~]# rabbitmqctl status
Status of node 'rabbit@overcloud-controller-0' ...
[{pid,28553},
 {running_applications,[{rabbit,"RabbitMQ","3.3.5"},
                        {mnesia,"MNESIA  CXC 138 12","4.11"},
                        {os_mon,"CPO  CXC 138 46","2.2.14"},
                        {xmerl,"XML parser","1.3.6"},
                        {sasl,"SASL  CXC 138 11","2.3.4"},
                        {stdlib,"ERTS  CXC 138 10","1.19.4"},
                        {kernel,"ERTS  CXC 138 10","2.16.4"}]},
 {os,{unix,linux}},
 {erlang_version,"Erlang R16B03-1 (erts-5.10.4) [source] [64-bit] [smp:2:2] [async-threads:30] [hipe] [kernel-poll:true]\n"},
 {memory,[{total,95687312},
          {connection_procs,6336968},
          {queue_procs,4641232},
          {plugins,0},
          {other_proc,13701016},
          {mnesia,915272},
          {mgmt_db,0},
          {msg_index,199752},
          {other_ets,1034272},
          {binary,44341976},
          {code,16704609},
          {atom,1902833},
          {other_system,5909382}]},
 {alarms,[]},
 {listeners,[{clustering,35672,"::"},{amqp,5672,"192.0.2.11"}]},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,2013111910},
 {disk_free_limit,50000000},
 {disk_free,38070566912},
 {file_descriptors,[{total_limit,924},
                    {total_used,145},
                    {sockets_limit,829},
                    {sockets_used,143}]},
 {processes,[{limit,1048576},{used,1994}]},
 {run_queue,0},
 {uptime,192145}]
...done.

Comment 3 John Eckersberg 2015-08-19 15:04:53 UTC
upstream pr - https://github.com/puppetlabs/puppetlabs-rabbitmq/pull/381

Comment 4 James Slagle 2015-08-19 21:02:44 UTC

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