> Jason,
> just to get sure that we're on the same page here:
> - You have a two node cluster
yes
> - You have a resource that is running only on one node
yes
> - When you run the resource on node b, node a reports for that
> resource a failed monitor?
No (at least as I understand you)
When the resource is active, the 'hb-vxvol monitor' returns 0. When
the resource is stopped, the 'hb-vxvol monitor' returns 7. Otherwise,
it returns 1.
I have just validated the following:
1) If the resource is running on Node1, the 'monitor' action returns 0
on node1 and 7 on node2
2) If the resource is running on Node2, the 'monitor' action returns 7
on node1 and 0 on node2.
As I understand it, this is the correct implementation. If it's not,
please let me know.
If I shutdown the cluster completely with 'heartbeat stop' on both
nodes, then simultaneously start the cluster on both nodes, and watch
'crm_mon -i 1' on both nodes, the 'order of events' seems to be:
1) It nominates a node as DC (in this case, node2, though I've seen both)
2) The 'failed actions' block get's these lines almost immediately:
resource_samba_storage_monitor_0 (node=node2.domain.com,
call=3, rc=9): Error
resource_samba_storage_monitor_0 (node=node1.domain.com,
call=3, rc=9): Error
3) then the resource group starts in order on node2. (IP, then
storage, then daemon)
I'm not sure if this answers your questions. But the 'monitor' action
seems to be running for some reason before the resource actually
starts somewhere.
--Jason
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
