[Linux-HA] LRM_RSC_IDLE/LRM_RSC_BUSY

Junko IKEDA ikedaj at intellilink.co.jp
Sun Oct 28 22:13:44 MDT 2007


> > if it's LRM_RSC_BUSY,
> > a fail count would be increased,
> > and a return code was set as 14 (EXECRA_STATUS_UNKNOWN ?).
> 
> That should not have anything to do with it. If the resource is
> busy, the requested operation will be postponed until it becomes
> idle. The CRM handles such a situation.

Do you mean that if RA is busy, CRM will wait until it becomes idle?
It seems that CRM doesn't wait.

lrmd[9049]: 2007/10/29_12:47:35 debug: on_msg_get_state:state of rsc
prmDummy is LRM_RSC_BUSY
crmd[9136]: 2007/10/29_12:47:35 WARN: msg_to_op(1173): failed to get the
value of field lrm_opstatus from a ha_msg
...
crmd[9136]: 2007/10/29_12:47:35 WARN: msg_to_op(1173): failed to get the
value of field lfailcount: Updating failcount for prmDummy on
9d9ca527-cea9-470c-9e03-e49fe5630bba after failed monitor: rc=14


> A resource is busy whenever there's an operation running, i.e.
> such as monitor. Idle is the opposite.

I used a modified Dummy resource to emulate a delay of monitoring operation.
This RA is calling "sleep 50" immediately after monitoring.
(see attached Dummy RA)
I wonder it might cause RA's busy status.

Thanks,
Junko

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Dummy
Type: application/octet-stream
Size: 4914 bytes
Desc: not available
URL: <http://lists.linux-ha.org/pipermail/linux-ha/attachments/20071029/d2a6f2a1/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hb_report.tar.gz
Type: application/octet-stream
Size: 70105 bytes
Desc: not available
URL: <http://lists.linux-ha.org/pipermail/linux-ha/attachments/20071029/d2a6f2a1/attachment-0001.obj>


More information about the Linux-HA mailing list