This parameter can be used to force a service to run on the same node running other services.
This parameter can be used to help a service to run on the same node running other services.
This parameter can be used to force a service to avoid execution on the same node running other services.
This parameter can be used to help a service try to avoid execution on the same node running other services.
This parameter is used to specify the daemon behaviour regarding service orchestration
This setting is used to identify the best node to start the service on.
A boolean expression evaluated in order to constrain the service instance placement to nodes where expression is True.
This parameter is used to store a list of services that must be avail up for the agent daemon to proceed on starting the service.
The parents must be in the same cluster.
This parameter is used to store a list of services that must be avail down for the agent daemon to proceed on stopping the service.
A boolean mandating the stale node previously running the service to be shot by the daemon monitor upon failover.
Defaults to false.
Activates the scaler mode. An integer setting the target number of running instances of this service. To meet this target, the scaler clones itself as slave services. If the scaler topology is a flex, the flex_min_nodes and flex_max_nodes of each slave is automatically adjusted by the daemon.
Defaults to None.
Janitored by the join and leave nodemgr daemon actions.
default. Users can set it to a more meaningful value.
Changing that parameter on a joined cluster will break communications until the nodes share the same cluster.name, thus cause a massive split-brain situation. So take care of freezing the cluster nodes before.