1. Installing and Configuring HA for MySQL
Installing and Configuring HA for MySQL
Planning the HA for MySQL Installation and Configuration
Restriction for the HA for MySQL Data Service Configuration
Restrictions on the MySQL Configuration File
Restrictions for the MySQL Configurations
Restrictions on the MySQL Database Directory
Restriction for the MySQL smf Service Name in an HA Container
Examples for the File Systems Layout
Components and Their Dependencies for HA for MySQL
Registration and Configuration File for HA for MySQL
Explanation of the my.cnf File
Installing and Configuring MySQL
Enabling MySQL to Run in a Global Zone Configuration
How to Enable MySQL for a Failover Resource
How to Enable MySQL to Run in a Scalable Configuration
How to Enable MySQL to Run in a Multiple-Master Configuration
How to Install and Configure MySQL in a Global Zone
Enabling MySQL to Run in a Zone Configuration
How to Enable MySQL for a Failover Resource
How to Enable MySQL to Run in a Scalable Configuration
How to Enable MySQL to Run in a Multiple-Master Configuration
How to Install and Configure MySQL in a Zone
How to Enable MySQL to run in an HA Container Configuration
How to Install and Configure MySQL in an HA Container
Verifying the Installation and Configuration of MySQL
How to Verify the Installation and Configuration of MySQL
Installing the HA for MySQL Packages
How to Install the HA for MySQL Packages
Registering and Configuring HA for MySQL
How to Register and Configure HA for MySQL as a Failover Service in a Global Zone Configuration
How to Register and Configure HA for MySQL as a Failover Service in a Zone Configuration
How to Register and Configure HA for MySQL as a Failover Service in an HA Container Configuration
How to Modify Parameters in the HA for MySQL Manifest
How to Remove an HA for MySQL Resource From an HA Container
How to Add an HA for MySQL Resource in a Scalable or Multiple-Master Configuration
Verifying the HA for MySQL Installation and Configuration
How to Verify the HA for MySQL Installation and Configuration
Understanding the HA for MySQL Fault Monitor
Probing Algorithm and Functionality
Upgrade to Oracle Solaris Cluster 3.3 When Using HA for MySQL
Upgrade From Sun Cluster 3.1 8/05 to Oracle Solaris Cluster 3.3 When Using HA for MySQL
Upgrade to MySQL 4.x.x From 3.23.54 When Using HA for MySQL
Upgrade to MySQL Version 4.x.x From Version 3.23.54
A. Deployment Example: Installing MySQL in the Global Zone
B. Deployment Example: Installing MySQL in the Non-Global HA Container
C. Deployment Example: Installing MySQL in a Non-Global Zone
D. Deployment Example: Installing MySQL in a Scalable or Multiple-Master Configuration
HA for MySQL has a file named config that enables you to activate debugging for MySQL resources. This file is in the /opt/SUNWscmys/etc directory.
If your operating system is Solaris 10 and your MySQL resource is dependent on a Solaris Container boot component resource, you are in an HA container configuration. In any other case, especially on a Solaris 9 system, you are in a global zone configuration.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
If debugging is inactive, daemon.notice is set in the file /etc/syslog.conf of the appropriate zone.
If debugging is active, daemon.debug is set in the file /etc/syslog.conf.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.debug;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
Solaris 9:
# pkill -1 syslogd
Solaris 10:
# svcadm refresh svc:/system/system-log:default
The value of component-name can be ndb_mgmd, ndbd, ndbd_shutdown.
To debug all resources, use DEBUG=ALL
To debug specific resources, use DEBUG=resource name,resource name, ...
Note - To deactivate debugging, repeat this procedure, changing daemon.debug to daemon.notice and changing the DEBUG variable to DEBUG=.
Example 1-4 Editing the Debug Config File
# cat /opt/SUNWscmys/etc/config # # Copyright 2006 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # Usage: # DEBUG=<RESOURCE_NAME> or ALL # DEBUG=ALL #