Controller Database Configurations

You can make database configuration changes using:

  • Database Configuration UI Page
  • Enterprise Console CLI

Database Configuration UI Page

Use the Database Configuration UI page to edit your MySQL settings. This is helpful since you do not have to tweak the configuration file on the database host.

If your RAM memory is greater than 200 GB and you are using a NUMA based architecture, you can specify the Linux nodes (typically CPU socket numbers) from which both processes and memory will be allocated for each Splunk AppDynamics On-Premises component. For example on a two-socket motherboard, we recommend the following node configuration settings:

  • Glassfish should should allocate its threads/processes and memory on the first node: 0.
  • MySQL should allocate its threads/processes and memory on the second node: 1.
Note: For the node configuration settings, you can enter an integer or comma separated list of integers. For example, for Glassfish, you can enter 0 or 0,1; for MySQL, you can enter 1 or 2,3.

The configurations include:

  • DB Configuration Settings

    Data Directory: You can change the datadir path and database port via this page.

    Note: You cannot change certain configurations, such as the MySQL root directory, through the Enterprise Console.

  • DB Root Password

    The Enterprise Console allows you to reset the Controller MySQL root user password. See Change the Controller Database Root User Password.

Enterprise Console CLI

You can update the Controller database configuration programmatically using the Enterprise Console CLI. This enables you to preserve configuration settings during an upgrade.

Note:
  • If you are using High Availability Toolkit (HATK), you must manually apply these settings on the secondary Controller and restart the secondary server.
  • These instructions are specific to the UNIX operating system.

To update the database configuration using CLI:

  1. Copy the db.cnf file from your primary Controller host onto the Enterprise Console host, for example db.cnf.new file.
  2. Edit the db.cnf.new file to add new settings or update existing values.

  3. Load the db.cnf.new file into an environment variable:

    new_db_cnf=`cat db.cnf.new`

  4. Go to the platform-admin/bin directory and log in:

    ./platform-admin.sh login --user-name=admin --password=password

  5. Run the following command on the Enterprise Console host:

    bin/platform-admin.sh submit-job --service controller --job db-update-config --args mysqlCnfContent="$new_db_cnf"