[Pacemaker] About behavior in "Action Lost".
renayama19661014 at ybb.ne.jp
renayama19661014 at ybb.ne.jp
Tue Sep 21 06:59:48 UTC 2010
Hi,
Node was in state that the load was very high, and we confirmed monitor movement of Pacemeker.
Action Lost occurred in stop movement after the error of the monitor occurred.
Sep 8 20:02:22 cgl54 crmd: [3507]: ERROR: print_elem: Aborting transition, action lost: [Action 9]:
In-flight (id: prmApPostgreSQLDB1_stop_0, loc: cgl49, priority: 0)
Sep 8 20:02:22 cgl54 crmd: [3507]: info: abort_transition_graph: action_timer_callback:486 -
Triggered transition abort (complete=0) : Action lost
For the load of the node, We think that the stop movement did not go well.
But cannot nodes execute stonith.
When Action Lost occurred in stop movement, crmd do not seem to update cib.
Action Lost of the stop movement seems to make the transition that is in a state again hereby.
(snip)
gboolean
action_timer_callback(gpointer data)
{
(snip)
} else {
/* fail the action */
gboolean send_update = TRUE;
const char *task = crm_element_value(timer->action->xml, XML_LRM_ATTR_TASK);
print_action(LOG_ERR, "Aborting transition, action lost: ", timer->action);
timer->action->failed = TRUE;
timer->action->confirmed = TRUE;
abort_transition(INFINITY, tg_restart, "Action lost", NULL);
update_graph(transition_graph, timer->action);
trigger_graph();
if(timer->action->type != action_type_rsc) {
send_update = FALSE;
} else if(safe_str_eq(task, "cancel")) {
/* we dont need to update the CIB with these */
send_update = FALSE;
} else if(safe_str_eq(task, "stop")) {
/* *never* update the CIB with these */
send_update = FALSE;
}
if(send_update) {
/* cib_action_update(timer->action, LRM_OP_PENDING, EXECRA_STATUS_UNKNOWN); */
cib_action_update(timer->action, LRM_OP_TIMEOUT, EXECRA_UNKNOWN_ERROR);
}
}
return FALSE;
}
In Action Lost of the stop movement, is it specifications that stonith does not execute?
By setting, can we execute stonith?
Best Regards,
Hideo Yamauchi.
More information about the Pacemaker
mailing list