Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Service for MySQL Cluster Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Example Configuration Files for Installation in the Global Zone

This section contains example contents for the following files:

- `config.ini` File for Both Nodes to Store in `/mgm-data`

- `my.cnf` File for the Data Nodes to Store in `/ndbd-data`

- `my.cnf` File for the First SQL Node `phys-schost-1` to Store in `/mysql-data`

- `my.cnf` File for the Second SQL Node `phys-schost-2` to Store in `/mysql-data`

- `mysql_config` File for the First SQL Node `phys-schost-1` to Store in `/temp/cluconfig`

- `mysql_config` File for the Second SQL Node `phys-schost-2` to Store in `/temp/cluconfig`

- `mysql_ndb_mgmd_config` File for the First Node `phys-schost-1`

- `mysql_ndb_mgmd_config` File for the Second Node `phys-schost-2`

- `mysql_ndbd_config` File for the First Node `phys-schost-2`

- `mysql_ndbd_config` File for the Second Node `phys-schost-2`

- `ndbd_shutdown_config` File for One Node

- `ha_mysql_config` File for One Node

### `config.ini` File for Both Nodes to Store in `/mgm-data`

    [TCP DEFAULT]
    SendBufferMemory=2M
    ReceiveBufferMemory=2M

    [NDB_MGMD DEFAULT]
    PortNumber=1186
    Datadir=/mgm-data/

    [NDB_MGMD]
    Id=1
    Hostname=phys-schost-1-p

    [NDB_MGMD]
    Id=2
    Hostname=phys-schost-2-p

    [NDBD DEFAULT]
    NoOfReplicas=2
    Datadir=/ndbd-data/
    DataMemory=256M
    IndexMemory=32M
    LockPagesInMainMemory=0
    StopOnError=FALSE
    Arbitration=WaitExternal
    ArbitrationTimeout=10000

    MaxNoOfConcurrentOperations=100000

    StringMemory=25
    MaxNoOfTables=4096
    MaxNoOfOrderedIndexes=2048
    MaxNoOfUniqueHashIndexes=512
    MaxNoOfAttributes=24576
    DiskCheckpointSpeedInRestart=100M
    FragmentLogFileSize=256M
    InitFragmentLogFiles=FULL
    NoOfFragmentLogFiles=3
    RedoBuffer=32M

    TimeBetweenLocalCheckpoints=20
    TimeBetweenGlobalCheckpoints=1000
    TimeBetweenEpochs=100

    MemReportFrequency=30
    BackupReportFrequency=10

    ### Params for setting logging
    LogLevelStartup=15
    LogLevelShutdown=15
    LogLevelCheckpoint=8
    LogLevelNodeRestart=15

    ### Params for increasing disk throughput
    BackupMaxWriteSize=1M
    BackupDataBufferSize=16M
    BackupLogBufferSize=4M
    BackupMemory=20M
    #Reports indicate that odirect=1 can cause io errors (os err code 5) on some systems. You must test.
    #ODirect=1

    ### Watchdog
    TimeBetweenWatchdogCheckInitial=30000

    ### TransactionInactiveTimeout - should be enabled in Production
    #TransactionInactiveTimeout=30000
    ### CGE 6.3 - REALTIME EXTENSIONS
    #RealTimeScheduler=1
    #SchedulerExecutionTimer=80
    #SchedulerSpinTimer=40

    ### DISK DATA
    #SharedGlobalMemory=384M
    #DiskPageBufferMemory=3072M

    ### Multithreading
    MaxNoOfExecutionThreads=2
    BatchSizePerLocalScan=512
    [NDBD]
    Id=3
    Hostname=phys-schost-1-p

    ### CGE 6.3 - REALTIME EXTENSIONS
    ### PLEASE NOTE THAT THE BELOW ONLY WORKS IF YOU HAVE >1 CORE.
    ### YOU SHOULD CHECK cat /proc/interrupts AND CHOOSE THE CPUs
    ### THAT GENERATE THE LEAST INTERRUPS. TYPICALLY THE CPU HANDLING
    ### THE INTERRUPTS FOR THE COMMUNICATION INTERFACE USED FOR THE DATA NODE SHOULD
    ### BE AVOIDED FOR THE LockExecuteThreadToCPU, BUT YOU CAN
    ### LockMaintThreadsToCPU TO THAT CPU SINCE IT DOES NOT AFFECT THE
    ### REALTIME ASPECTS (THIS IS TRUE FOR UP TO TWO DATA NODES ON ONE COMPUTER.
    #LockExecuteThreadToCPU=X
    #LockMaintThreadsToCPU=Y

    [NDBD]
    Id=4
    Hostname=phys-schost-2-p

    ### CGE 6.3 - REALTIME EXTENSIONS
    ### PLEASE NOTE THAT THE BELOW ONLY WORKS IF YOU HAVE >1 CORE.
    ### YOU SHOULD CHECK cat /proc/interrupts AND CHOOSE THE CPUs
    ### THAT GENERATE THE LEAST INTERRUPS. TYPICALLY THE CPU HANDLING
    ### THE INTERRUPTS FOR THE COMMUNICATION INTERFACE USED FOR THE DATA NODE SHOULD
    ### BE AVOIDED FOR THE LockExecuteThreadToCPU, BUT YOU CAN
    ### LockMaintThreadsToCPU TO THAT CPU SINCE IT DOES NOT AFFECT THE
    ### REALTIME ASPECTS (THIS IS TRUE FOR UP TO TWO DATA NODES ON ONE COMPUTER.
    #LockExecuteThreadToCPU=X
    #LockMaintThreadsToCPU=Y

    ##   BELOW ARE TWO (INACTIVE) SLOTS FOR DATA NODES TO ALLOW FOR GROWTH
    #[NDBD]
    #Id=5
    #Hostname=

    ### CGE 6.3 - REALTIME EXTENSIONS
    ### PLEASE NOTE THAT THE BELOW ONLY WORKS IF YOU HAVE >1 CORE.
    ### YOU SHOULD CHECK cat /proc/interrupts AND CHOOSE THE CPUs
    ### THAT GENERATE THE LEAST INTERRUPS. TYPICALLY THE CPU HANDLING
    ### THE INTERRUPTS FOR THE COMMUNICATION INTERFACE USED FOR THE DATA NODE SHOULD
    ### BE AVOIDED FOR THE LockExecuteThreadToCPU, BUT YOU CAN
    ### LockMaintThreadsToCPU TO THAT CPU SINCE IT DOES NOT AFFECT THE
    ### REALTIME ASPECTS (THIS IS TRUE FOR UP TO TWO DATA NODES ON ONE COMPUTER.
    #LockExecuteThreadToCPU=X
    #LockMaintThreadsToCPU=Y

    #[NDBD]
    #Id=6
    #Hostname=

    ### CGE 6.3 - REALTIME EXTENSIONS
    ### PLEASE NOTE THAT THE BELOW ONLY WORKS IF YOU HAVE >1 CORE.
    ### YOU SHOULD CHECK cat /proc/interrupts AND CHOOSE THE CPUs
    ### THAT GENERATE THE LEAST INTERRUPS. TYPICALLY THE CPU HANDLING
    ### THE INTERRUPTS FOR THE COMMUNICATION INTERFACE USED FOR THE DATA NODE SHOULD
    ### BE AVOIDED FOR THE LockExecuteThreadToCPU, BUT YOU CAN
    ### LockMaintThreadsToCPU TO THAT CPU SINCE IT DOES NOT AFFECT THE
    ### REALTIME ASPECTS (THIS IS TRUE FOR UP TO TWO DATA NODES ON ONE COMPUTER.
    #LockExecuteThreadToCPU=X
    #LockMaintThreadsToCPU=Y

    [MYSQLD DEFAULT]
    BatchSize=512
    #BatchByteSize=2048K
    #MaxScanBatchSize=2048K

    [MYSQLD]
    Id=7
    Hostname=phys-schost-1

    [MYSQLD]
    Id=8
    Hostname=phys-schost-2

### `my.cnf` File for the Data Nodes to Store in `/ndbd-data`

    # Options for ndbd process:
    [mysql_cluster]
    ndb-connectstring=phys-schost-1-p:1186,phys-schost-2-p:1186 # location of management server

### `my.cnf` File for the First SQL Node `phys-schost-1` to Store in `/mysql-data`

    [mysqld]
    server-id=1
    #port=3306
    socket=/tmp/phys-schost-1.sock
    log=/mysql-data/logs/log1
    log-bin=/mysql-data/logs/bin-log
    binlog-ignore-db=sc3_test_database
    log-slow-queries=/mysql-data/logs/log-slow-queries
    #log-update=/mysql-data/logs/log-update

    # Innodb
    #skip-innodb
    loose-innodb_data_home_dir = /mysql-data/innodb
    loose-innodb_data_file_path = ibdata1:10M:autoextend
    loose-innodb_log_group_home_dir = /mysql-data/innodb
    #innodb_log_arch_dir = /mysql-data/innodb
    # You can set .._buffer_pool_size up to 50 - 80 %
    # of RAM but beware of setting memory usage too high
    loose-set-variable = innodb_buffer_pool_size=50M
    loose-set-variable = innodb_additional_mem_pool_size=20M
    # Set .._log_file_size to 25 % of buffer pool size
    loose-set-variable = innodb_log_file_size=12M
    loose-set-variable = innodb_log_buffer_size=4M
    loose-innodb_flush_log_at_trx_commit=1
    loose-set-variable = innodb_lock_wait_timeout=50

    # MySQL 4.x
    relay-log=/mysql-data/logs/slave-bin.log
    relay-log-info-file=/mysql-data/logs/slave-info

    # changes for cluster
    #[mysqld]
    ndbcluster
    ndb-connectstring=phys-schost-1,phys-schost-2

    # provide connectstring for management server host (default port: 1186)
    [ndbd]
    connect-string=phys-schost-1,phys-schost-2

    # provide connectstring for management server host (default port: 1186)
    [ndb_mgm]
    connect-string=phys-schost-1,phys-schost-2

    # provide location of cluster configuration file
    [ndb_mgmd]
    config-file=/mgm-data/config.ini

### `my.cnf` File for the Second SQL Node `phys-schost-2` to Store in `/mysql-data`

    [mysqld]
    server-id=1
    #port=3306
    socket=/tmp/phys-schost-2.sock
    log=/mysql-data/logs/log1
    log-bin=/mysql-data/logs/bin-log
    binlog-ignore-db=sc3_test_database
    log-slow-queries=/mysql-data/logs/log-slow-queries
    #log-update=/mysql-data/logs/log-update

    # Innodb
    #skip-innodb
    loose-innodb_data_home_dir = /mysql-data/innodb
    loose-innodb_data_file_path = ibdata1:10M:autoextend
    loose-innodb_log_group_home_dir = /mysql-data/innodb
    #innodb_log_arch_dir = /mysql-data/innodb
    # You can set .._buffer_pool_size up to 50 - 80 %
    # of RAM but beware of setting memory usage too high
    loose-set-variable = innodb_buffer_pool_size=50M
    loose-set-variable = innodb_additional_mem_pool_size=20M
    # Set .._log_file_size to 25 % of buffer pool size
    loose-set-variable = innodb_log_file_size=12M
    loose-set-variable = innodb_log_buffer_size=4M
    loose-innodb_flush_log_at_trx_commit=1
    loose-set-variable = innodb_lock_wait_timeout=50

    # MySQL 4.x
    relay-log=/mysql-data/logs/slave-bin.log
    relay-log-info-file=/mysql-data/logs/slave-info

    # changes for cluster
    #[mysqld]
    ndbcluster
    ndb-connectstring=phys-schost-1,phys-schost-2

    # provide connectstring for management server host (default port: 1186)
    [ndbd]
    connect-string=phys-schost-1,phys-schost-2

    # provide connectstring for management server host (default port: 1186)
    [ndb_mgm]
    connect-string=phys-schost-1,phys-schost-2

    # provide location of cluster configuration file
    [ndb_mgmd]
    config-file=/mgm-data/config.ini

### `mysql_config` File for the First SQL Node `phys-schost-1` to Store in `/temp/cluconfig`

    # Where is MySQL installed (BASEDIR)
    MYSQL_BASE=/usr/local/mysql

    # MySQL admin-user for localhost (Default is root)
    MYSQL_USER=root

    # Password for MySQL admin user
    MYSQL_PASSWD=root

    # Configured logicalhost
    MYSQL_HOST=phys-schost-1

    # Specify a username for a faultmonitor user
    FMUSER=fmuser

    # Pick a password for that faultmonitor user
    FMPASS=

    # Socket name for mysqld ( Should be /tmp/logical-host.sock )
    MYSQL_SOCK=/tmp/phys-schost-1.sock

    # Specify the physical hostname for the
    # physical NIC that this logicalhostname belongs to for every node in the
    # cluster this resource group is located on.
    # IE: The logicalhost lh1 belongs to hme1 for physical-node phys-1 and
    # hme3 for physical-node phys-2. The hostname for hme1 is phys-1-hme0 and
    # for hme3 on phys-2 it is phys-2-hme3.
    # IE: MYSQL_NIC_HOSTNAME="zone1"
    MYSQL_NIC_HOSTNAME="phys-schost-1 phys-schost-2"

    MYSQL_DATADIR=/mysql-data
    # Is MySQL Cluster installed?
    # Any entry here triggers the ndb engine check. If no MySQL cluster should be checked
    # leave it empty.
    NDB_CHECK=y

### `mysql_config` File for the Second SQL Node `phys-schost-2` to Store in `/temp/cluconfig`

    # Where is MySQL installed (BASEDIR)
    MYSQL_BASE=/usr/local/mysql

    # MySQL admin-user for localhost (Default is root)
    MYSQL_USER=root

    # Password for MySQL admin user
    MYSQL_PASSWD=root

    # Configured logicalhost
    MYSQL_HOST=phys-schost-2

    # Specify a username for a faultmonitor user
    FMUSER=fmuser

    # Pick a password for that faultmonitor user
    FMPASS=

    # Socket name for mysqld ( Should be /tmp/logical-host.sock )
    MYSQL_SOCK=/tmp/phys-schost-2.sock

    # Specify the physical hostname for the
    # physical NIC that this logicalhostname belongs to for every node in the
    # cluster this resource group is located on.
    # IE: The logicalhost lh1 belongs to hme1 for physical-node phys-1 and
    # hme3 for physical-node phys-2. The hostname for hme1 is phys-1-hme0 and
    # for hme3 on phys-2 it is phys-2-hme3.
    # IE: MYSQL_NIC_HOSTNAME="zone1"
    MYSQL_NIC_HOSTNAME="phys-schost-1 phys-schost-2"

    MYSQL_DATADIR=/mysql-data
    # Is MySQL Cluster installed?
    # Any entry here triggers the ndb engine check. If no MySQL cluster should be checked
    # leave it empty.
    NDB_CHECK=y

### `mysql_ndb_mgmd_config` File for the First Node `phys-schost-1`

    # This file will be sourced in by mysql_ndb_mgmd_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #    RS - Name of the resource for the application
    #    RG - Name of the resource group containing RS
    #
    # MySQL Cluster ndb_nmbd specific variables
    #
    # SCALABLE - Any value here triggers a scalable resource creation
    # LB_POLICY - Set the loadbalancing policy for a scalable mysql service.
    #       Use the values defined for the standard resource property
    #       Load_balancing_policy. If you do not specify it, the defaults are
    #       used.
    #    LH - Name of the Shared Address SC resource
    #  HAS_RS - Name of the MySQL HAStoragePlus SC resource
    #  RS_PROP - Additional resource properties in the format for clresource create,
    #     example "-p start_timeout=600"
    #  PARFILE - Absolute path to the management server resource parameter file
    #
    #    The following examples illustrate sample parameters
    #    for a multiple-master MySQL Cluster management server resource.
    #
    #    RS=mgm-rs
    #    RG=mgm-rg
    #    PORT=1186
    #    SCALABLE=
    #    HAS_RS=
    #    PARFILE=/ndb-mgmd-data/pfile
    #

    RS=mgm-rs
    RG=mgm-rg
    PORT=1186
    LH=sa_host_1
    SCALABLE=yes
    LB_POLICY=
    HAS_RS=
    RS_PROP=
    PARFILE=/cluster-pfiles/mgmd-pfile

    #    This is the template for a MySQL cluster's management server resource.
    #    The variables must be specified in the key value form.
    #    BASEDIR    Directory where MySQL cluster is installed, to find the binaries.
    #    USER      User under which the management server will be run. An empty value
    #           stands for the root user.
    #    TRY_RECONNECT Value for the try-reconnect parameter in the mgm command.
    #    CONNECT_STRING A connect string which is valid for any connection to the management
    #           server.
    #    CONFIG_DIR   Directory where the management server's config.ini file and its cache
    #           files are stored.
    #    ID       Unique ID for this management server. This value must match the entry
    #           in the config.ini file.
    #
    #    Examples:
    #    BASEDIR=/usr/local/mysql
    #    USER=
    #    TRY_RECONNECT=1
    #    CONNECT_STRING=phys-node-1,phys-node-2
    #    CONFIG_DIR=/ndb-nmbd-data
    #    ID=1
    #

    BASEDIR=/usr/local/mysql
    USER=
    TRY_RECONNECT=1
    CONNECT_STRING=phys-schost-1,phys-schost-2
    CONFIG_DIR=/mgm-data
    ID=1

### `mysql_ndb_mgmd_config` File for the Second Node `phys-schost-2`

    # This file will be sourced in by mysql_ndb_mgmd_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #    RS - Name of the resource for the application
    #    RG - Name of the resource group containing RS
    #
    # Mysql cluster ndb_nmbd specific Variables
    #
    # SCALABLE - Any value here triggers a scalable resource creation
    # LB_POLICY - Set the loadbalancing policy for a scalable mysql service.
    #       Use the values defined for the standare resource property
    #       Load_balancing_policy. If you do not specify it, the defaults are
    #       used.
    #    LH - Name of the LogicalHostname SC resource
    #  HAS_RS - Name of the MySQL HAStoragePlus SC resource
    #  RS_PROP - Additional resource properties in the format for clresource create,
    #     example "-p start_timeout=600"
    #  PARFILE - Absolute path to the management server resource parameter file
    #
    #    The following examples illustrate sample parameters
    #    for the MySQL Cluster management server resource.
    #
    #    SCALABLE=yes
    #    NETWORK=
    #    HAS_RS=
    #    RS_PROP=
    #    PARFILE=/ndb-mgmd-data/pfile
    #

    RS=mgm-rs
    RG=mgm-rg
    PORT=1186
    LH=sa_host_1
    SCALABLE=yes
    LB_POLICY=
    HAS_RS=
    RS_PROP=
    PARFILE=/cluster-pfiles/mgmd-pfile

    #    This is the template for a MySQL cluster's management server resource.
    #    The variables must be specified in the key value form.
    #    BASEDIR    Directory where MySQL cluster is installed, to find the binaries.
    #    USER      User under which the management server will be run. An empty value
    #           stands for the root user.
    #    TRY_RECONNECT Value for the try-reconnect parameter in the mgm command.
    #    CONNECT_STRING A connect string which is valid for any connection to the management
    #           server.
    #    CONFIG_DIR   Directory where the management server's config.ini file and its cache
    #           files are stored.
    #    ID       Unique Id for this management server, this value must match the entry
    #           in the config.ini file.
    #
    #    Examples:
    #    BASEDIR=/usr/local/mysql/bin
    #    USER=
    #    TRY_RECONNECT=1
    #    CONNECT_STRING=phys-node-1,phys-node-2
    #    CONFIG_DIR=/ndb-nmbd-data
    #    ID=1
    #

    BASEDIR=/usr/local/mysql
    USER=
    TRY_RECONNECT=1
    CONNECT_STRING=phys-schost-2,phys-schost-1
    CONFIG_DIR=/mgm-data
    ID=2

### `mysql_ndbd_config` File for the First Node `phys-schost-2`

    # This file will be sourced in by mysql_ndbd_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #    RS - Name of the resource for the application
    #    RG - Name of the resource group containing RS
    #
    # MySQL cluster ndb_nmbd specific variables
    #
    #  HAS_RS - Name of the MySQL HAStoragePlus SC resource
    #  RS_PROP - Additional resource properties in the format for clresource create,
    #     example "-p start_timeout=600"
    #  PARFILE - Absolute path to the data node resource parameter file
    #
    #    The following examples illustrate sample parameters
    #    for the MySQL Cluster data node resource.
    #
    #    RS=ndbd-rs
    #    RG=ndbd-rg
    #    HAS_RS=
    #    RS_PROP=
    #    PARFILE=/ndb-mgmd-data/pfile
    #

    RS=ndbd-rs
    RG=ndbd-rg
    HAS_RS=mgm-rs
    RS_PROP=
    PARFILE=/cluster-pfiles/ndbd-pfile

    #    This is the template for a MySQL cluster's management server resource.
    #    The variables must be specified in the key value form.
    #    BASEDIR    Directory where MySQL cluster is installed, to find the binaries.
    #    USER      User under which the management server will be run. An empty value
    #           stands for the root user.
    #    TRY_RECONNECT Value for the try-reconnect parameter in the mgm command.
    #    CONNECT_STRING A connect string which is valid for any connection to the management
    #           server.
    #    ID       Unique ID for this management server. This value must match the entry
    #           in the config.ini file.
    #    MULTI_THREAD  Any entry here will trigger the start of the multithreaded version ndbmtd
    #           of the ndbd instead of the single-threaded version ndbd.
    #    DATA_DIR    Data directory of the ndb process.
    #    ERROR_ON_SHOW Return code if the probe is unable to connect to the management server.
    #
    #    Examples:
    #    BASEDIR=/usr/local/mysql/bin
    #    USER=
    #    TRY_RECONNECT=1
    #    CONNECT_STRING=phys-node-1,phys-node-2
    #    ID=1
    #    DATAG_DIR=/ndb-data
    #    MULTI_THREAD=yes
    #    ERROR_ON_SHOW=25
    #

    BASEDIR=/usr/local/mysql
    USER=
    TRY_RECONNECT=1
    CONNECT_STRING=phys-schost-1-p,phys-schost-2-p
    ID=3
    MULTI_THREAD=y
    DATA_DIR=/ndbd-data
    ERROR_ON_SHOW=25

### `mysql_ndbd_config` File for the Second Node `phys-schost-2`

    # This file will be sourced in by mysql_ndbd_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #    RS - Name of the resource for the application
    #    RG - Name of the resource group containing RS
    #
    # MySQL cluster ndb_nmbd specific variables
    #
    #  HAS_RS - Name of the MySQL HAStoragePlus SC resource
    #  RS_PROP - Additional resource properties in the format for clresource create,
    #     example "-p start_timeout=600"
    #  PARFILE - Absolute path to the data node resource parameter file
    #
    #    The following examples illustrate sample parameters
    #    for the MySQL Cluster data node resource.
    #
    #    HAS_RS=
    #    RS_PROP=
    #    PARFILE=/ndb-mgmd-data/pfile
    #

    RS=ndbd-rs
    RG=ndbd-rg
    HAS_RS=mgm-rs
    RS_PROP=
    PARFILE=/cluster-pfiles/ndbd-pfile

    #    This is the template for a MySQL clusters management server resource.
    #    The variables must be specified in the key value form.
    #    BASEDIR    Directory where MySQL cluster is installed, to find the binaries.
    #    USER      User under which the management server will be run, an empty value
    #           stands for the root user.
    #    TRY_RECONNECT Value for the try-reconnect parameter in the mgm command.
    #    CONNECT_STRING A connect string which is valid for any connection to the management
    #           server.
    #    ID       Unique ID for this management server, this value must match the entry
    #           in the config.ini file.
    #    MULTI_THREAD  Any entry here will trigger the start of the multithreaded version ndbmtd
    #           of the ndbd instead of the single-threaded version ndbd.
    #    DATA_DIR    Data directory of the ndb process.
    #    ERROR_ON_SHOW Return code if the probe is unable to connect to the management server.
    #
    #    Examples:
    #    BASEDIR=/usr/local/mysql/bin
    #    USER=
    #    TRY_RECONNECT=1
    #    CONNECT_STRING=phys-node-1,phys-node-2
    #    ID=1
    #    DATA_DIR=/ndb-data
    #    MULTI_THREAD=yes
    #    ERROR_ON_SHOW=25
    #

    BASEDIR=/usr/local/mysql
    USER=
    TRY_RECONNECT=1
    CONNECT_STRING=phys-schost-1-p,phys-schost-2-p
    ID=4
    MULTI_THREAD=y
    DATA_DIR=/ndbd-data
    ERROR_ON_SHOW=25

### `ndbd_shutdown_config` File for One Node

    # This file will be sourced in by mysql_ndbd_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #    RS - Name of the resource for the application
    #    RG - Name of the resource group containing RS
    #
    # MySQL cluster ndb_nmbd specific variables
    #
    #  HAS_RS - Name of the MySQL HAStoragePlus SC resource
    #  RS_PROP - Additional resource properties in the format for clresource create,
    #     example "-p start_timeout=600"
    #  PARFILE - Absolute path to the data node resource parameter file
    #       IMPORATANT: it is essential to specify the data node
    #       parameter file.
    #
    #    The following examples illustrate sample parameters
    #    for the MySQL Cluster ndb shutdown resource.
    #
    #    HAS_RS=ndbd-rs
    #    RS_PROP=
    #    PARFILE=/ndb-mgmd-data/pfile
    #

    RS=ndbd-shut-rs
    RG=ndbd-rg
    HAS_RS=ndbd-rs
    RS_PROP=
    PARFILE=/cluster-pfiles/ndbd-pfile

### `ha_mysql_config` File for One Node

    # This file will be sourced in by ha_mysql_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #    RS - Name of the resource for the application
    #    RG - Name of the resource group containing RS
    # SCALABLE - Flag to indicate a scalable resource creation.
    #       The default is no, so any entry here triggers a scalable resource.
    # LB_POLICY - Set the loadbalancing policy for a scalable MySQL service.
    #       Use the values defined for the standare resource property
    #       Load_balancing_policy. If you do not specify it, the defaults are
    #       used.
    #  RS_PROP - Additional resource properties in the format for clresource create,
    #     example "-p start_timeout=600"
    #  PROJECT - A project in the zone that will be used for this service
    #       Specify it if you have an su - in the start stop or probe,
    #       or to define the smf credentials. If the variable is not set,
    #       it will be translated as :default for the sm and default
    #       for the zsh component
    #       Optional
    #   ZUSER - A user in the the zone which is used for the smf method
    #       credentials. Your smf service will run under this user
    #       Optional
    #
    #  BASEDIR - Name of the MySQL bin directory
    #  DATADIR - Name of the MySQL Data directory
    # MYSQLUSER - Name of the user Mysql should be started of
    #    LH - Name of the LogicalHostname SC resource
    # MYSQLHOST - Name of the host in /etc/hosts
    #  FMUSER - Name of the MySQL fault monitor user
    #  FMPASS - Name of the MySQL fault monitor user password
    #  LOGDIR - Name of the directory mysqld should store it's logfile.
    #  CHECK - Should HA-MySQL check MyISAM index files before start YES/NO.
    #  HAS_RS - Name of the MySQL HAStoragePlus SC resource
    #
    #    The following examples illustrate sample parameters
    #    for MySQL
    #
    #    BASEDIR=/usr/local/mysql
    #    DATADIR=/global/mysqldata
    #    MYSQLUSER=mysql
    #    LH=mysqllh
    #    MYSQLHOST=mysqllh
    #    FMUSER=fmuser
    #    FMPASS=
    #    LOGDIR=/global/mysqldata/logs
    #    CHECK=YES
    #

    RS=mys-rs
    RG=mysql-rg
    PORT=3306
    SCALABLE=yes
    LB_POLICY=
    LH=sa_host_1
    HAS_RS=ndbd-shut-rs
    RS_PROP=
    # Local zone specific options

    ZONE=
    ZONE_BT=
    ZUSER=
    PROJECT=

    # MySQL specifications

    BASEDIR=/usr/local/mysql
    DATADIR=/mysql-data
    MYSQLUSER=mysql
    MYSQLHOST=
    FMUSER=fmuser
    FMPASS=
    LOGDIR=/mysql-data/logs
    CHECK=YES
    NDB_CHECK=YES

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |