Configuring the MariaDB service - Adaptive Applications - BlueCat Gateway - 23.2.3

BlueCat Distributed DDNS Administration Guide

Product name
BlueCat Gateway
By default the MariaDB database service is configured when you deploy a Distributed DDNS Data Node. You can modify the configuration information through the MariaDB service configuration.
Note: By default, the General Log and Slow Query Logs are disabled and the Error Log is written to stderr. If you modify these settings and with to revert the settings to the default configuration, you must redeploy the Data Node container.
  1. If it's not already displayed, click the Database Nodes tab.

  2. In the Manage DB Nodes table, in the MariaDB column, click the Settings gear icon for the row of the node you want to manage. This icon will be different colors (typically  green) depending on the service status.

  3. In the MariaDB configuration window, the following information appears (your details might vary slightly):

    # MariaDB database server configuration file.
    # You can copy this file to one of:
    # - "/etc/mysql/my.cnf" to set global options,
    # - "~/.my.cnf" to set user-specific options.
    # One can use all long options that the program supports.
    # Run program with --help to get a list of available options and with
    # --print-defaults to see which it would actually understand and use.
    # For explanations see
    # This will be passed to all mysql clients
    # It has been reported that passwords should be enclosed with ticks/quotes
    # especially if they contain "#" chars...
    # Remember to edit /etc/mysql/debian.cnf when changing the socket location.
    port = 3306
    socket = /var/run/mysqld/mysqld.sock
    # Here is entries for some specific programs
    # The following values assume you have at least 32M ram
    # This was formally known as [safe_mysqld]. Both versions are currently parsed.
    socket = /var/run/mysqld/mysqld.sock
    nice = 0
    # * Basic Settings
    #user = mysql
    pid-file = /var/run/mysqld/
    socket = /var/run/mysqld/mysqld.sock
    port = 3306
    basedir = /usr
    datadir = /var/lib/mysql
    tmpdir = /tmp
    lc_messages_dir = /usr/share/mysql
    lc_messages = en_US
    # Instead of skip-networking the default is now to listen only on
    # localhost which is more compatible and is not less secure.
    #bind-address =
    # * Fine Tuning
    max_connections = 1,000
    connect_timeout = 5
    wait_timeout = 600
    max_allowed_packet = 16M
    thread_cache_size = 128
    sort_buffer_size = 4M
    bulk_insert_buffer_size = 16M
    tmp_table_size = 32M
    max_heap_table_size = 32M
    # * MyISAM
    # This replaces the startup script and checks MyISAM tables if needed
    # the first time they are touched. On error, make copy and try a repair.
    myisam_recover_options = BACKUP
    key_buffer_size = 128M
    #open-files-limit = 2000
    table_open_cache = 400
    myisam_sort_buffer_size = 512M
    concurrent_insert = 2
    read_buffer_size = 2M
    read_rnd_buffer_size = 1M
    # * Query Cache Configuration
    # Cache only tiny result sets, so we can fit more in the query cache.
    query_cache_limit = 128K
    query_cache_size = 64M
    # for more write intensive setups, set to DEMAND or OFF
    #query_cache_type = DEMAND
    # * Logging and Replication
    # Both location gets rotated by the cronjob.
    # Be aware that this log type is a performance killer.
    # As of 5.1 you can enable the log at runtime!
    general_log_file = /var/log/mysql/mariadb.log
    general_log = 1
    # Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
    log_error = /var/log/mysql/mariadb.err
    # we do want to know about network errors and such
    log_warnings = 2
    # Enable the slow query log to see queries with especially long duration
    slow_query_log = 1
    slow_query_log_file = /var/log/mysql/mariadb-slow.log
    long_query_time = 10
    #log_slow_rate_limit = 1000
    #log_slow_verbosity = query_plan
    # The following can be used as easy to replay backup logs or for replication.
    # note: if you are setting up a replication slave, see README.Debian about
    #       other settings you may need to change.
    #server-id = 1
    #report_host = master1
    #auto_increment_increment = 2
    #auto_increment_offset = 1
    #log_bin = /var/log/mysql/mariadb-bin
    #log_bin_index = /var/log/mysql/mariadb-bin.index
    # not fab for performance, but safer
    #sync_binlog = 1
    expire_logs_days = 10
    max_binlog_size = 100M
    # slaves
    #relay_log = /var/log/mysql/relay-bin
    #relay_log_index = /var/log/mysql/relay-bin.index
    #relay_log_info_file = /var/log/mysql/
    # If applications support it, this stricter sql_mode prevents some
    # mistakes like inserting invalid dates etc.
    # * InnoDB
    # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
    # Read the manual for more InnoDB related options. There are many!
    default_storage_engine = InnoDB
    innodb_buffer_pool_size = 256M
    innodb_log_buffer_size = 8M
    innodb_file_per_table = 1
    innodb_open_files = 400
    innodb_io_capacity = 400
    innodb_flush_method = O_DIRECT
    # * Security Features
    # Read the manual, too, if you want chroot!
    # chroot = /var/lib/mysql/
    # For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
    # * Galera-related settings
    # Mandatory settings
    wsrep_on = ON
    wsrep_provider = /usr/lib/galera/
    wsrep_cluster_address = gcomm://,,
    wsrep_cluster_name = rc2-cluster
    wsrep_node_name = node_10.245.6.32
    wsrep_node_address =
    wsrep_sst_receive_address =
    wsrep_provider_options = "gmcast.listen_addr=tcp://[::]:4567; socket.ssl_cert=/etc/ddns_ssl/mysql/mariadb_server_cert.pem; socket.ssl_key=/etc/ddns_ssl/mysql/mariadb_server_key.pem; socket.ssl_ca=/etc/ddns_ssl/ca/ca_cert.pem"
    wsrep_notify_cmd = /usr/local/bin/wsrep_notify
    binlog_format = row
    default_storage_engine = InnoDB
    innodb_autoinc_lock_mode = 2
    # Allow server to accept connections on all interfaces.
    bind-address = ::
    # Optional setting
    wsrep_slave_threads = 1
    innodb_flush_log_at_trx_commit = 0
    max_allowed_packet = 16M
    #no-auto-rehash	# faster start of mysql but no tab completion
    key_buffer = 16M
    # * IMPORTANT: Additional settings that can override those from this file!
    #   The files must end with '.cnf', otherwise they'll be ignored.
    !include /etc/mysql/mariadb.cnf
    !includedir /etc/mysql/conf.d/
    Where parameters are as follows:
    • ssl_ca = /etc/ddns_ssl/ca/ca_cert.pem: Defines the path to a PEM file that contains one or more X509 certificates for the trusted Certificate Authorities (CAs) to use for TLS. This system variable must be entered as an absolute path to the file.

      Note: BlueCat advises against modifying this setting.
    • ssl_cert = /etc/ddns_ssl/mysql/mariadb_server_cert.pem: Defines the path to the X509 certificate to use for TLS. This system variable must be entered as an absolute path to the file.

      Note: BlueCat advises against modifying this setting.
    • ssl_key = /etc/ddns_ssl/mysql/mariadb_server_key.pem: Defines the path to the private key to use for TLS. This system variable must be entered as an absolute path to the file.

      Note: BlueCat advises against modifying this setting.
    • wsrep_cluster_address = gcomm://<cluster-address-list>: The IP addresses of cluster notes to connect to when starting up the container. For example, gcomm://

      BlueCat recommends specifying all possible cluster nodes in the following format: gcomm://<node1 or ip1:port>,<node2 or ip2:port>,<node3 or ip3:port>.

      If you specify an empty gcomm:// field, the node will start a new cluster. This should not be done in the my.cnf file, as the server will not rejoin the current cluster after the container is restarted.

      The variable can be modified as runtime in some configurations, resulting in the node closing the connection to any existing cluster and connecting to a new address. If you specify a port when entering an IP address, note that the port is the Galera port and not the MariaDB port.

      Note: BlueCat advises against modifying this setting.
    • wsrep_cluster_name = <cluster-name>: The name of the database cluster. Nodes cannot connect to clusters with different names. This variable can be configured dynamically but changing this value unloads and reloads the wsrep provider. Misconfiguring this field can result in an outage.

      Note: BlueCat advises against modifying this setting.
    • wsrep_node_name = <node-name>: The name of this node. The name can be used in wsrep_sst_donor as a preferred donor. You can configure multiple nodes in a cluster with the same name.

      Note: BlueCat advises against modifying this setting.
    • wsrep_node_address = <node_address>: The network address of the node in the following format: <ip_address>[:<port>]. The network address supports IPv4 and IPv6 configuration.

      By default, the node pulls the address of the first network interface on the system and the default Galera port. This behavior can be unreliable in the following cases:
      • Cloud deployments
      • Container deployments
      • Servers with multiple network interfaces
      • Servers with multiple nodes
      • Network address translation (NAT)
      • Clusters with nodes in more than one region
      Note: BlueCat advises against modifying this setting.
    • wsrep_sst_receive_address = <node_address>: The address where other nodes (donor) in the cluster connect to sent the state-transfer updates. If an address is not configured or is set to AUT0 (default), the mysqld process uses the value of --wsrep_node_address as the receiving address. If --wsrep_node_address is not configured, the address from either --bind-address is used or it tries to retrieve an address from the list of available network interfaces, in that order.

      • Setting this parameter to localhost makes it impossible for nodes running on other hosts to reach this host.

      • BlueCat advises against modifying this setting.

    • For more information on the MySQL configuration fields, see the MySQL documentation on the MySQL website.

    • For more information on the Galera configuration fields, see the Galera documentation on the MariaDB website.

  4. When you're done, click Save to save the Distributed DDNS service configuration.

  5. After the changes are saved, click Start to start the service and add it to the Distributed DDNS Service Node.