| 2015-05-14 13:53:56 |
Assaf Muller |
description |
From the rabbit server log:
=INFO REPORT==== 12-May-2015::18:21:04 ===
Disk free space insufficient. Free bytes:974610432 Limit:1000000000
=WARNING REPORT==== 12-May-2015::18:21:04 ===
disk resource limit alarm set on node rabbit@localhost.
**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************
If a disk or RAM rabbitmq alarm goes off:
https://www.rabbitmq.com/alarms.html
All connections will be blocked:
[stack@localhost ~]$ sudo rabbitmqctl list_connections
Listing connections ...
stackrabbit 10.0.0.200 42587 blocking
stackrabbit 10.0.0.200 42588 blocking
...
The user experience in Oslo messaging here is very poor: There's just no indication whatsoever. There's no timeouts on RPC calls, they just freeze indefinitely. There's no error in any log in any OpenStack service. |
From the rabbit server log:
=INFO REPORT==== 12-May-2015::18:21:04 ===
Disk free space insufficient. Free bytes:974610432 Limit:1000000000
=WARNING REPORT==== 12-May-2015::18:21:04 ===
disk resource limit alarm set on node rabbit@localhost.
**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************
If a disk or RAM rabbitmq alarm goes off:
https://www.rabbitmq.com/alarms.html
All connections will be blocked:
[stack@localhost ~]$ sudo rabbitmqctl list_connections
Listing connections ...
stackrabbit 10.0.0.200 42587 blocking
stackrabbit 10.0.0.200 42588 blocking
...
The user experience in Oslo messaging here is very poor: There's just no indication whatsoever. There's no timeouts on RPC calls, they just freeze indefinitely. There's no error in any log in any OpenStack service. I'm not familiar with the rabbit driver backend, I'm hoping that it would be possible to get an error out of it somehow. |
|
