On Tue, Nov 29, 2011 at 12:54 AM, <alain.mou...@bull.net> wrote:
> Hi
>
> I always have this problem.
> Just a little question : when this occurs, meaning a monitoring happening
> whereas there is
> just a crm command request on the resource i.e. migration, why not just
> return SUCCESS
> so that the next monitoring on this resource will be executed on the good
> node ? instead
> of delaying the monitoring a few seconds after, and when the resouce is
> obviously no more
> on the same node ?
The monitor op shouldn't be executed at all.
We cancel them before initiating the migration:
/* stop the monitor before stopping the resource */
if (crm_str_eq(operation, CRMD_ACTION_STOP, TRUE)
|| crm_str_eq(operation, CRMD_ACTION_DEMOTE, TRUE)
|| crm_str_eq(operation, CRMD_ACTION_PROMOTE, TRUE)
|| crm_str_eq(operation, CRMD_ACTION_MIGRATE, TRUE)) {
g_hash_table_foreach_remove(pending_ops,
stop_recurring_action_by_rsc, rsc);
}
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
