Configuration of MySQLCltOperTest

The MySQL Cluster distributed database helps in providing high availability and throughput for the MySQL database management system. If a user complains that his/her transactions with My SQL Cluster database are failing, administrators may first want to know which steps of the user interactions are failing often. The MySQLCltOperTest provides administrators with this useful information.

This test periodically monitors the status of the MySQL Cluster database server. Using the test, administrators an proactively be alerted when the cluster is non operational/stopped. In addition, this test throws light on the operations that were completed successfully and the operations that failed.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the HOST for which this test is to be configured.

• In the PORT text box, specify the port at which the target host is listening. The default port is 3306.

• Specify the full path to the location where the target MySQL Cluster manager is installed in MCM PATH textbox. For example, your location can be C:\Users\user\AppData\Roaming/mcmd.conf. By default, none is specified against this parameter.

• To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.