Comment 2 for bug 1493520

Expected behaviour: pacemaker should mark this node offline and migrate resources.
It doesn't happen because monitor scripts check processes and open sockets. In case of full root file system sockets are still open and processes are still running. But rabbitmq doesn't provide the service and returns
 =WARNING REPORT====
disk resource limit alarm set on node 'rabbit@node-2'.
**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************

It could be fixed in monitor scripts: try to send message and stop resource in case of few fails
Or in osco.messaging: choose another rabbitmq in case of this warning

Actually we have separate logic volumes for frequently variable files. And we can provide this improvements as a feature in 8.0