On Fri, Jan 15, 2010 at 8:39 PM, jaspal singla <[email protected]> wrote: > Hello, > > Thanks for your prompt response and also I have some doubts, it will be if > these also will get cleared. > > Please find my inline queries: > > >> > group group_vz_1 vip_ipaddr2 filesystem1_Filesystem vz1_script \ >> > meta target-role="started" >> > group group_vz_2 vip2_ipaddr2 filesystem2_Filesystem vz2_script \ >> > meta target-role="started" >> > location location_master group_vz_1 700: node_master >> > location location_node3 group_vz_2 600: node3 >> > location location_slave_1 group_vz_1 0: node_slave >> > location location_slave_2 group_vz_2 0: node_slave >> > colocation colocation_vz_test -inf: group_vz_1 group_vz_2 >> >> The anti-collocation rule you have is correct, and this should result in >> the resources not being placed on the same node. >> > > Yes this configuration is working fine now as per my required scenario after > restart of the node_slave node but I don't know why after restart of the > node_slave the behavior became alright..
Did you attach a hb_report from before you rebooted node_slave? >> Disabling stonith is not a good idea if you're running shared storage. >> >> > For stonith integration, unfortunately I am using old hardware servers where > there is not any ILO such kind of ports and my management also don't want to > invest money for the APC Power switch.. > > Please suggest me Can I go for SSH based stonith mechanism for my Production > setup or better to leave my Production cluster without stonith? Neither is an option I would consider appropriate for a production cluster. > >> rsc_defaults $id="rsc_defaults-options" >> >> You may want to enable resource-stickiness to avoid resources shuffling >> around needlessly. >> >> > What is the use of default_resource-stickness value(If in case of we have > defined resource-stickiness value to all primitive resources)?? As I have > already defined the resource_stickiness value to my all primitive > resources.. If you have already defined it for every resource, then there is no need to supply a default as well. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
