[ClusterLabs] Antw: Understanding\Manually adjusting node-health-strategy

[Ulrich Windl]

>>> Ian Underhill <ianpunderhill at gmail.com> schrieb am 26.07.2018 um 19:44 in
Nachricht
<CAGu+cYhU=-yr182y-M6U+BVUFVOCKPhJTzDTuo-4+DQeyq7Vbg at mail.gmail.com>:
> when a resource fails on a node I would like to mark the node unhealthy, so
> other resources dont start up on it.
> 
> I believe I can achieve this, ignoring the concept of fencing at the moment.
> 
> I have tried to set my cluster to have a node-health-strategy as only_green.
> 
> However trying to manually adjust the nodes health, I believe I can set an
> attribute #health on a node (see ref docs) but trying to set any attribute
> #health???? fails?
> 
> # sudo crm_attribute --node myNode --name=#health --update=red
>       Error setting     #health=red (section=nodes, set=nodes-3): Update
> does not conform to the configured schema Error performing operation:
> Update does not conform to the configured schema

According to my cluster book the command should be like this:
attrd_updater -n "#health_test " -v red


> 
> Im slightly surprised I dont get "something for free" regarding pacemaker
> auto adjusting the health of a node when resources fail on it? am I missing
> a setting or is this done by hand.

It's simply because you cannot conclude from a resource failure tha the node per se has a problem. That's specifically true when you run many different kinds of resources.
Imagine one badly configured resource will mark all your nodes as unhealthy, forcing all resources to be stopped...

Regards,
Ulrich