On 2011-05-13 08:55, Maxim Ianoglo wrote: > Hello, > > I have the following configuration: > Nodes: Node_A and Node_B > > Resources: WWW ( gr_apache_www ), NFS Server ( gr_storage_server ), NFS > Client ( gr_storage_client ) > > Locations: > gr_apache_www: By Default on Node_A, failover to Node_B > gr_storage_server: By Default on Node_A, failover to Node_B > gr_storage_client: By Default on Node_A, "failovers" just in case Node_A was > brought back online but gr_storage_server will not be moved to it's default > location for now, but gr_apache_www will. > > Constraints: > colocation colo_storage -inf: gr_storage_client gr_storage_server > order ord_storage inf: gr_storage_server gr_storage_client > order ord_www inf: gr_storage_server ( gr_apache_www_main ) > order ord_www2 inf: gr_storage_client ( gr_apache_www_main ) > > Now I have the situation: > I put Node_A in standby so ALL resources should go to Node_B ( except for > gr_storage_client ), but for some reason only gr_storage_server is moved to > Node_B. > gr_apache_www is not even started. > > How can I make gr_apache_www start even if gr_storage_client is not running > anywhere ? But if it is running anywhere it should run after > gr_storage_client. >
order ord_www2 0: gr_storage_client gr_apache_www_main ... an advisory order constraint. Regards, Andreas > Configuration ( constraints and cluster options ): > ======================================================== > location loc_gr_apache_www_default gr_apache_www \ > rule $id="prefered_loc_gr_apache_default" 100: #uname eq Node_A > location loc_gr_apache_www_failover gr_apache_www \ > rule $id="prefered_loc_gr_apache_failover" 50: #uname eq Node_B > location loc_gr_storage_server_default gr_storage_server \ > rule $id="prefered_loc_gr_storage_server_default" 100: #uname eq > Node_A > location loc_gr_storage_server_failover gr_storage_server \ > rule $id="prefered_loc_gr_storage_server_failover" 50: #uname eq > Node_B > colocation colo_storage -inf: gr_storage_client gr_storage_server > order ord_nfslock_storage_client inf: gr_storage_client clone_nfslock > order ord_nfslock_storage_server inf: gr_storage_server clone_nfslock > order ord_storage inf: gr_storage_server gr_storage_client > order ord_www inf: gr_storage_server ( gr_nginx_static gr_apache_www_main ) > order ord_www2 inf: gr_storage_client ( gr_nginx_static gr_apache_www_main ) > property $id="cib-bootstrap-options" \ > symmetric-cluster="true" \ > no-quorum-policy="ignore" \ > stonith-enabled="false" \ > stonith-action="reboot" \ > startup-fencing="true" \ > stop-orphan-resources="true" \ > stop-orphan-actions="true" \ > remove-after-stop="false" \ > default-action-timeout="60s" \ > is-managed-default="true" \ > cluster-delay="60s" \ > pe-error-series-max="-1" \ > pe-warn-series-max="-1" \ > pe-input-series-max="-1" \ > dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \ > last-lrm-refresh="1305263051" \ > cluster-infrastructure="Heartbeat" > rsc_defaults $id="rsc-options" \ > resource-stickiness="100" > ======================================= > > Thank you. > -- > Maxim Ianoglo > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
