Configuration of MySQLTabSpcTest

In an effort to track the growth of individual databases in a MySQL cluster, administrators may want to time and again check how many rows of data each table in a cluster database contains. In the process, they will be able to identify those tables with more than a permissible number of records. Based on this finding, they can then decide whether deletion of a few or more unnecessary records from these ‘large tables’ can keep database growth under check. Similarly, to ensure that an instance in the cluster database does not grow uncontrollably, administrators have to periodically check the size of the database tables, isolate the tables with the maximum size, and see if the table size can somehow be reduced. The MySQLTabSpcTest test helps administrators in this exercise.

This test reports the total number of tables that contain more than a configured number of records and the total number of top tables in a given database in terms of size. The detailed diagnosis of this test will help administrators figure our the exact tables that has outgrown in records and size.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to choose how often should the test be executed.

• In the HOST text box, specify the IP address of the host for which the test is to be configured.

• In the PORT text box, specify the port at which the specified host listens.

• In the DATABASE text box specify the name of a database on the target MySQL database server being monitored.

• The eG agent has to be configured with the credentials of a user who has server-wide Process and Select privileges on the monitored MySQL server. Specify the credentials of such a user in the USERNAME and PASSWORD text boxes. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Server topic in the Monitoring MySQL Server document.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the TABLE ROWS text box specify the number of records beyond which this test will consider a table as a large table.

• In the TABLE SIZE (MB) text box specify the size of the table beyond which this test will consider a table as a large table.

• By default, the detailed diagnosis of this test, if enabled, will report only the top-10 tables. This is why, the DD ROW COUNT parameter is set to 10 by default. If you want to include more or less tables in detailed diagnosis, then change the value of this parameter accordingly.

• The DETAILED DIAGNOSIS makes diagnosis more efficient and accurate, the eG Enterprise 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 for a particular server, choose the On option. 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 normal and abnormal 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 check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the above values are provided, click on the UPDATE button to 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.