Rabbit OCF script doesn't reelect master in case of master node failure
Bug #1490941 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Matthew Mosesohn | ||
6.0.x |
Won't Fix
|
High
|
MOS Maintenance | ||
6.1.x |
Fix Committed
|
High
|
Denis Puchkin | ||
7.0.x |
Fix Released
|
High
|
Matthew Mosesohn |
Bug Description
Rabbit OCF script version 6.0, 6.1 both show the same behavior.
When master node experience issue with arp cache and rabbitmq is having problems to connect to localhost, rabbitmq ocf script keeps trying to bring rabbitmq up for minutes, cycling over start/stop/cleanup.
It's expected that it would elect new master node for rabbitmq and give up on bringing up rabbitmq on failing node.
This results in cloud outage.
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Bogdan Dobrelya (bogdando) |
status: | Incomplete → Confirmed |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
importance: | High → Wishlist |
tags: | added: support |
tags: | added: tricky |
no longer affects: | fuel/8.0.x |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: on-verification |
tags: | added: area-library |
To post a comment you must log in.
To create aforementioned problems with connection to localhost one need to reduce the size of arp cache: neigh.default. gc_thresh1 = 4 neigh.default. gc_thresh2 = 8 neigh.default. gc_thresh3 = 16
sysctl - w net.ipv4.
sysctl - w net.ipv4.
sysctl - w net.ipv4.