多MariaDB实例下客户端选项及mysqldump等工具配置咨询

Great question—managing multiple MariaDB instances with specialized configs can get messy if you don’t understand how the tooling reads settings. Let’s break this down clearly:

1. Scope of [mysqldump] / [myisamchk] Sections #

Unlike your instance-specific [mysqld.innodb] or [mysqld.myisam] blocks (which only load when starting that particular mariadb@instance service), [mysqldump] and [myisamchk] are client/utility-focused config sections. They’re not tied to a single mysqld instance—any time you run the mysqldump or myisamchk tool, it will read all matching sections from every config file in MariaDB’s config path.

2. Best Practice: Centralize Shared Configs #

Absolutely, you should move these shared utility settings into a single global file to avoid duplication across your instance-specific .cnf files. This cuts down on maintenance work (you only update one place instead of multiple files) and keeps your configs organized.

For example, create a dedicated file like /etc/my.cnf.d/client-utils.cnf with your shared defaults:

[mysqldump]
quick
max_allowed_packet = 64M
single-transaction  # Ideal for consistent InnoDB backups

[myisamchk]
key_buffer_size = 256M
sort_buffer_size = 256M

This file will be read by all invocations of mysqldump and myisamchk, no matter which MariaDB instance you’re targeting.

3. Instance-Specific Overrides (If Needed) #

If you ever need utility settings tailored to a specific instance (e.g., a larger packet size for a MyISAM instance with massive tables), you can add the same section to that instance’s config file. The instance-specific settings will override the global defaults for that tool invocation.

For example, in /etc/my.cnf.d/myisam.cnf:

[mysqld.myisam]
datadir = /var/lib/mysql-myisam
socket = /var/run/mysqld/mysqld-myisam.sock
port = 3307

# Override global mysqldump settings for this MyISAM instance
[mysqldump]
max_allowed_packet = 128M
lock-tables  # Better for MyISAM backups than single-transaction

When you run mysqldump against this instance (e.g., using -S /var/run/mysqld/mysqld-myisam.sock), MariaDB will load the global [mysqldump] settings first, then apply the instance-specific ones to overwrite duplicates.

4. No Impact on Instance Startup #

Don’t worry about these utility sections interfering with your mariadb@instance services. When you start mariadb@innodb, the service uses the --defaults-group-suffix=.innodb flag, which tells the mysqld process to only load [mysqld] and [mysqld.innodb] sections. The [mysqldump] and [myisamchk] blocks are completely ignored during instance startup—they only activate when you run those specific tools.

内容的提问来源于stack exchange，提问作者Tom Glare