![]() W/o this fix, the situation is possible when some arbitrary queue masters got stuck due to high short-time CPU load spikes ending up in the rabbitmqctl hanged and affected rabbit node erased and restarted by OCF monitor logic of the related pacemaker RA. This is an issue as it seems that Oslo.messaging yet to be in a good shape to survive this short-time outage of underlying AMQP layer without disrupting interrupted RPC calls being executed. The workaround is to reduce the net_ticktime kernel parameter from default 60 seconds to 10 seconds. What would allow the RabbitMQ cluster to better detect short-time partitions and autoheal them. And when the partition has been detected and healed, the rabbitmqctl would not hang hopefully as stucked queue masters will be recovered. Partial-bug: #1460762 Change-Id: I3aa47b51ae080bb4a8b298c61a629ac8225d2abd Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com> |
||
---|---|---|
debian | ||
deployment/puppet | ||
files | ||
specs | ||
tests/noop | ||
utils | ||
.gitignore | ||
.gitreview | ||
CHANGELOG | ||
LICENSE | ||
README.md |
Fuel is the Ultimate Do-it-Yourself Kit for OpenStack
Purpose built to assimilate the hard-won experience of our services team, it contains the tooling, information, and support you need to accelerate time to production with OpenStack cloud.
OpenStack is a very versatile and flexible cloud management platform. By exposing its portfolio of cloud infrastructure services – compute, storage, networking and other core resources — through ReST APIs, it enables a wide range of control over these services, both from the perspective of an integrated Infrastructure as a Service (IaaS) controlled by applications, as well as automated manipulation of the infrastructure itself.
This architectural flexibility doesn’t set itself up magically; it asks you, the user and cloud administrator, to organize and manage a large array of configuration options. Consequently, getting the most out of your OpenStack cloud over time – in terms of flexibility, scalability, and manageability – requires a thoughtful combination of automation and configuration choices.
Mirantis Fuel for OpenStack was created to solve exactly this problem.