Explanation of the my.cnf File

my.cnf file — The Sun Cluster HA for MySQL data service provides two sample my.cnf files, one sample file for a master configuration and one for a slave configuration. However, ensure that at least the following parameters are set.

The my.cnf file is a important file within MySQL. Refer to the MySQL Documentation for complete configuration information on the parameters that follow.

MySQL my.cnf file in [mysqld]section in a master configuration

• bind address must be set to the defined logical host's IP name.

  ---

  Note –

  Some MySQL do not work with bind address if the name of the logical host is set. In these cases do not set the bind address parameter, or use the absolute address of the logical hostname.

  ---

• socket is defined as /tmp/logical host's ip name.sock.

• binlog-ignore-db contains sc3_test_database, if log-bin option is being used.

MySQL my.cnf file in [mysqld]section in a slave configuration

• bind address must be set to the defined logical host's IP name.

  ---

  Note –

  Some MySQL builds do not work with names in the bind address parameter. In these cases do not set the bind address parameter, or use the absolute IP address of the logical hostname.

  ---

• socket is defined as /tmp/logical host's IP name.sock.

• binlog-ignore-db contains sc3_test_database if log-bin option is being used.

• master—host is the hostname where the master instance resides.

• master—user is the username the slave will use for identification to the master.

• master—password is the password the slave will use for identification to the master.

• master-info-file is the location of the file that remembers where MySQL left off on the master during the replication process. This file must be placed on a GFS/FFS.