Re: [Pacemaker] Unable to stop Multi state resource
On Tue, Apr 19, 2011 at 12:34 PM, Rakesh K wrote: > Rakesh K writes: > > > Hi Andrew > > FSR is a File system replication script which adheres to ocf cluster frame > work, > the script is similar to Mysql ocf script, which is a multi state resource, > where in master ssh server would be running and in slave there are rsync > scripts which uses to synchronize the data between the Master and slave. > > the rsync script will be having the Master FSR location, so that the rysnc > tool > will be frequently replication the data from the FSR master location. > > here is the crm configuration show output Thanks, but this doesn't really answer my question about whether the cluster tried to stop it. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Unable to stop Multi state resource
Rakesh K writes: Hi Andrew FSR is a File system replication script which adheres to ocf cluster frame work, the script is similar to Mysql ocf script, which is a multi state resource, where in master ssh server would be running and in slave there are rsync scripts which uses to synchronize the data between the Master and slave. the rsync script will be having the Master FSR location, so that the rysnc tool will be frequently replication the data from the FSR master location. here is the crm configuration show output node $id="82a5281a-a069-49c1-9f57-d4a8f6eb3d72" prodmsf2 node $id="d8b6c2e7-d1c3-4a15-9411-ed4d710c8672" prodmsf primitive FSR ocf:msf:fsr \ params client_script="/home/msf/ha/scripts/ocf/rsyncClient" source_dir="/home/msf/services/persistence/" dest_dir="/home/msf/services/persistence/" user="root" pid="/var/run/fsr.pid" rsync_binary="/usr/bin/rsync" rsync_options="-az" rsync_interval="1" config_file="/home/msf/ha/config/ocf/fsr.config" status_dump="/home/msf/ha/status/rsync_client_dump" \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="120s" \ op monitor interval="10s" role="Master" timeout="8s" \ op monitor interval="12s" timeout="8s" primitive Httpd ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" httpd="/usr/sbin/httpd" client="curl" statusurl="http://localhost/img/test.html"; testregex="*" \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="120s" \ op monitor interval="50s" timeout="50s" primitive HttpdVIP ocf:heartbeat:IPaddr3 \ params ip="10.10.30.103" eth_num="eth0:1" vip_cleanup_file="/var/run/bigha.pid" \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="120s" \ op monitor interval="30s" \ meta target-role="Started" primitive Mysql ocf:heartbeat:mysql \ params binary="/usr/bin/mysqld_safe" config="/etc/my.cnf" datadir="/var/lib/mysql" user="mysql" pid="/var/lib/mysql/mysql.pid" socket="/var/lib/mysql/mysql.sock" test_passwd="slavepass" test_table="test.conn" test_user="repl" replication_user="repl" replication_passwd="slavepass" \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="120s" \ op monitor interval="10s" role="Master" timeout="8s" \ op monitor interval="12s" timeout="8s" primitive MysqlVIP ocf:heartbeat:IPaddr3 \ params ip="10.10.30.105" eth_num="eth0:3" vip_cleanup_file="/var/run/bigha.pid" \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="60s" \ op monitor interval="30s" \ meta target-role="Started" primitive Tomcat1 ocf:msf:tomcat1 \ params tomcat_name="tomcat" statusurl="http://localhost:8080/"; java_home="/" catalina_home="/home/msf/runtime/tomcat/apache-tomcat-6.0.18" client="curl" testregex="*" \ op start interval="0" timeout="120s" \ op monitor interval="50s" timeout="50s" \ op stop interval="0" timeout="120s" \ meta target-role="Started" primitive Tomcat1VIP ocf:heartbeat:IPaddr3 \ params ip="10.10.30.104" eth_num="eth0:2" vip_cleanup_file="/var/run/bigha.pid" \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="120s" \ op monitor interval="30s" \ meta target-role="Started" ms MS_FSR FSR \ meta notify="true" target-role="Started" ms MS_Mysql Mysql \ meta notify="true" target-role="Started" colocation FSR-with-Tomcat inf: Tomcat1 MS_FSR:Master colocation Httpd-with-ip inf: HttpdVIP Httpd colocation Mysql-with-ip inf: MysqlVIP MS_Mysql:Master colocation Tomcat1-with-ip inf: Tomcat1VIP Tomcat1 order FSR-after-tomcat inf: Tomcat1 MS_FSR order Httpd-after-ip inf: HttpdVIP Httpd order Httpd-after-tomcat inf: Tomcat1 HttpdVIP order Mysql-after-ip inf: MysqlVIP MS_Mysql order Tomcat1-after-MYSQL inf: MS_Mysql Tomcat1VIP order Tomcat1-after-ip inf: Tomcat1VIP Tomcat1 property $id="cib-bootstrap-options" \ dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \ cluster-infrastructure="Heartbeat" \ stonith-enabled="false" \ no-quorum-policy="ignore" Regards Rakesh ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Unable to stop Multi state resource
Andrew Beekhof writes: Hi Andrew FSR is file system replication, like Mysql multi-state resource, it replicates the files from master to all the slaves in the cluster frame work. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Unable to stop Multi state resource
On Thu, Apr 14, 2011 at 9:02 AM, rakesh k wrote: > Hi All > > I had configure heartbeat with 2 node cluster and 7 resources > > The list of resources are Tomcat,apachehttpd,Mysql and FSR where mysql and > FSR are multi-state resource. > > and i had given order and co-location constraints please find the crm > configuration for order and co-location > > colocation FSR-with-Tomcat inf: Tomcat1 MS_FSR:Master > colocation Httpd-with-ip inf: HttpdVIP Httpd > colocation Mysql-with-ip inf: MysqlVIP MS_Mysql:Master > colocation Tomcat1-with-ip inf: Tomcat1VIP Tomcat1 > order FSR-after-tomcat inf: Tomcat1 MS_FSR > order Httpd-after-op inf: HttpdVIP Httpd > order Mysql-after-ip inf: MysqlVIP MS_Mysql > order Tomcat1-after-MYSQL inf: MS_Mysql Tomcat1VIP > order Tomcat1-after-ip inf: Tomcat1VIP Tomcat1 > > now my question is on the two node cluster when i am stopping MS_Mysql > multistate resource using crm resource stop MS_Mysql, as per the above order > given all the process should stop on the cluster frame work, but still i am > finding FSR process running. is there any error in the order or co-location > constraints provided. please let me know, i am running out of time.. What is the FSR resource? Does the cluster try to stop the FSR resource? It would say so in the logs. > > One more concern for Pacemaker > > is the mailer -link available when it would be up. > > http://news.gmane.org/gmane.linux.highavailability.pacemaker > > is there any new link created for this mailer-list. > I have no idea what this means. > Regards > Raki > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
