7 More Discussions You Might Find Interesting
1. Gentoo
How to failover the cluster ? GNU/Linux
By which command,
My Linux version
2008 x86_64 x86_64 x86_64 GNU/Linux
What are the prerequisites we need to take while failover ?
if any
Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies
2. IP Networking
All,
I am looking to setup a simple IP failover setup, but it seems every place i look has some difficult setup like pacemaker or LVS.
I only want to handle the IP piece to failover a VIP.
Any suggestions? I checked out keepalived and that my work for me. (4 Replies)
Discussion started by: markdjones82
4 Replies
3. Solaris
Hi guys,
I'm running vxdmp and powerpath at the same time. Vxdmp for internal disks and powerpath for external.
The problem is that, on the failover tests which a fiber cable should be removed, the system cannot recognize the disks.
Any hints on how to configure powerpath in order to... (4 Replies)
Discussion started by: glenioborges
4 Replies
4. AIX
Hi All,
How do I trigger the failover on the second hacmp server?
Please give me idea and I will do the rest.
Thanks,
itik (2 Replies)
Discussion started by: itik
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have 3 directories (/1 /2 and /3) with same contents and want to achieve fail over among them.
The Solution i thought of:
1. link /data to /1 (and provide users with /data to access)
2. CRON a script (to run every minute) to verify if /1 exist or not, if it does not exist (or its... (3 Replies)
Discussion started by: prvnrk
3 Replies
6. Solaris
Hai,
I am having ultra machine where SUN o.s 5.6 is installed with Clusters 2.2. Here, i am facing a problem of Cluster switchover oftenly. Can you suggest a solution.
Madan (1 Reply)
Discussion started by: madanrajan
1 Replies
7. Solaris
Would anyone know why a V440 Solaris 9 machine's interfaces (ce0 and ce1)
will not failover?
Both interfaces are on the same subnet, but different IPs. I can pull the plug on once interface (ce0) and ce1 will be accessible. I can reverse it and pull ce1, and ce0 will NOT be accessible. ... (5 Replies)
Discussion started by: StorageGuy
5 Replies
OCF_HEARTBEAT_MYSQL(7) OCF resource agents OCF_HEARTBEAT_MYSQL(7)
NAME
ocf_heartbeat_mysql - Manages a MySQL database instance
SYNOPSIS
mysql [start | stop | status | monitor | promote | demote | meta-data | validate-all]
DESCRIPTION
Resource script for MySQL. May manage a standalone MySQL database, a clone set with externally managed replication, or a complete
master/slave replication setup.
While managing replication, the default behavior is to use uname -n values in the change master to command. Other IPs can be specified
manually by adding a node attribute ${INSTANCE_ATTR_NAME}_mysql_master_IP giving the IP to use for replication. For example, if the mysql
primitive you are using is p_mysql, the attribute to set will be p_mysql_mysql_master_IP.
SUPPORTED PARAMETERS
binary
Location of the MySQL server binary
(optional, string, default "/usr/bin/safe_mysqld")
client_binary
Location of the MySQL client binary
(optional, string, default "mysql")
config
Configuration file
(optional, string, default "/etc/my.cnf")
datadir
Directory containing databases
(optional, string, default "/var/lib/mysql")
user
User running MySQL daemon
(optional, string, default "mysql")
group
Group running MySQL daemon (for logfile and directory permissions)
(optional, string, default "mysql")
log
The logfile to be used for mysqld.
(optional, string, default "/var/log/mysqld.log")
pid
The pidfile to be used for mysqld.
(optional, string, default "/var/run/mysql/mysqld.pid")
socket
The socket to be used for mysqld.
(optional, string, default "/var/lib/mysql/mysql.sock")
test_table
Table to be tested in monitor statement (in database.table notation)
(optional, string, default "mysql.user")
test_user
MySQL test user, must have select privilege on test_table
(optional, string, default "root")
test_passwd
MySQL test user password
(optional, string, no default)
enable_creation
If the MySQL database does not exist, it will be created
(optional, boolean, default 0)
additional_parameters
Additional parameters which are passed to the mysqld on startup. (e.g. --skip-external-locking or --skip-grant-tables)
(optional, string, no default)
replication_user
MySQL replication user. This user is used for starting and stopping MySQL replication, for setting and resetting the master host, and
for setting and unsetting read-only mode. Because of that, this user must have SUPER, REPLICATION SLAVE, REPLICATION CLIENT, and
PROCESS privileges on all nodes within the cluster. Mandatory if you define a master-slave resource.
(optional, string, no default)
replication_passwd
MySQL replication password. Used for replication client and slave. Mandatory if you define a master-slave resource.
(optional, string, no default)
replication_port
The port on which the Master MySQL instance is listening.
(optional, string, default "3306")
max_slave_lag
The maximum number of seconds a replication slave is allowed to lag behind its master. Do not set this to zero. What the cluster
manager does in case a slave exceeds this maximum lag is determined by the evict_outdated_slaves parameter.
(optional, integer, default 3600)
evict_outdated_slaves
If set to true, any slave which is more than max_slave_lag seconds behind the master has its MySQL instance shut down. If this
parameter is set to false in a primitive or clone resource, it is simply ignored. If set to false in a master/slave resource, then
exceeding the maximum slave lag will merely push down the master preference so the lagging slave is never promoted to the new master.
(optional, boolean, default false)
reader_attribute
An attribute that the RA can manage to specify whether a node can be read from. This node attribute will be 1 if it's fine to read from
the node, and 0 otherwise (for example, when a slave has lagged too far behind the master).
A typical example for the use of this attribute would be to tie a set of IP addresses to MySQL slaves that can be read from.
This parameter is only meaningful in master/slave set configurations.
(unique, optional, string, default "readable")
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 120.
stop
Stops the resource. Suggested minimum timeout: 120.
status
Performs a status check. Suggested minimum timeout: 60.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 20.
monitor (Master role)
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.
monitor (Slave role)
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 30.
promote
Promotes the resource to the Master role. Suggested minimum timeout: 120.
demote
Demotes the resource to the Slave role. Suggested minimum timeout: 120.
notify
Suggested minimum timeout: 90.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a mysql resource using the crm(8) shell:
primitive p_mysql ocf:heartbeat:mysql
op monitor depth="0" timeout="30" interval="20"
op monitor role="Master" depth="0" timeout="30" interval="10"
op monitor role="Slave" depth="0" timeout="30" interval="30"
ms ms_mysql p_mysql
meta notify="true" interleave="true"
SEE ALSO
http://www.linux-ha.org/wiki/mysql_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_MYSQL(7)
