Rabbitmq pacemaker resource instances may start/stop simultaneously (ordered=false)
Bug #1515235 reported by
Bogdan Dobrelya
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
Medium
|
Michael Polenchuk | ||
Bug Description
Andrew pointed out http://
that for A/A case, instances of a clone might work better if configured with ordered=false.
For Fuel rabbitmq clustering, that might give a boost to a cluster bootstrap time, including failover cases.
All instances would join/recover in parallel rather than one by one, which might be *much* longer.
| Changed in fuel: | |
| importance: | Undecided → Medium |
| milestone: | none → 8.0 |
| assignee: | nobody → Fuel Library Team (fuel-library) |
| tags: | added: area-library |
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| assignee: | Fuel Library Team (fuel-library) → Michael Polenchuk (mpolenchuk) |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
Fuel configures the clone with ordered=false as well. Hence, invalid