[Freeswitch-users] FreeSWITCH Core - Cassandra Database

[Nathan Neulinger]

> For the floating IP to follow to the new box, on a *2* node setup, you
> need to disable quorum and add a constraint in your pacemaker/corosync
> config so the resource (PerconaDB) follows the floating IP. Something like:
>
> $ pcs property set no-quorum-policy=ignore
> $ pcs constraint colocation add PerconaDB ClusterIP INFINITY
> $ pcs constraint order ClusterIP then PerconaDB

I had something along those lines w/ a three-node cluster. I think this was close to the last config I used:


node $id="1945540483" freesw-db1.srv.mst.edu
node $id="1962317699" freesw-db2.srv.mst.edu
node $id="1979094915" freesw-db3.srv.mst.edu \
	attributes standby="off"
primitive p_ip_mysql ocf:heartbeat:IPaddr2 \
	params nic="eth0:0" iflabel="mysql" ip="131.151.246.119"
primitive p_mysql ocf:heartbeat:mysql \
	params config="/local/mysql/mysql.conf" \
		pid="/local/mysql/data/mysqld.pid" \
		socket="/var/lib/mysql/mysql.sock" \
		binary="/local/mysql/server/bin/mysqld" \
		datadir="/local/mysql/data" \
		log="/local/mysql/data/log" \
		additional_parameters="--basedir=/local/mysql/server --log-error=/local/mysql/data/log" \
	op monitor interval="30s" timeout="30s" \
	op start interval="0" timeout="120s" \
	op stop interval="0" timeout="120s"

clone cl_mysql p_mysql \
	meta interleave="true"

colocation c_ip_mysql inf: p_ip_mysql cl_mysql

property $id="cib-bootstrap-options" \
	dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \
	cluster-infrastructure="corosync" \
	stonith-enabled="false"

rsc_defaults $id="rsc-options" \
	resource-stickiness="100"





> I'm curious, did you use a shared filesystem (something like DRBD with
> GFS2/OCFS2) and regular Percona XtraDB on both nodes or did you use
> Percona XtraDB Cluster?

Percona XtraDB Cluster.

The symptom/problem I ran into - aside from Corosync/PM being excessively complex for the situation - was that a DB 
instance failed, and despite the others being online and the cluster itself being up and working - it didn't fail the IP 
over. It may have been a glitch - didn't see it during testing - but just more trouble than it was worth for the limited 
use case.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       nneul at mst.edu
Missouri S&T Information Technology    (573) 612-1412
System Administrator - Architect