Comment 1 for bug 1463433
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote Re: rabbitmq was down on one of controllers | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
As far as I can see the timestamp of the first "timed out waiting for reply" error fits into the described failover scope, see
https:/
So, we should debug this case deeply. Hopefully, some developer from MOS Oslo team could help us here.
As for underlying AMQP layer, as I mentioned earlier, I see no issues but a clean failover
My guess, that we have a classic AP+ C-case here, which is at least two amqp nodes was available (A+), partition was recovered (P+), some reply_queues was lost (C-) but the app layer have failed to survive such a lost.