- discuss - lists.mariadb.org

Support for galera clusters
by Dan O'Reilly 05 Dec '24

05 Dec '24

I can't find a place in the galera docs for a problem I'm having, so asking here. I have a 3 node mariadb Galera cluster (2 db's and an arbitrator node). On the arbitrator, when I start gardb manually and specify the log file as -l "/var/log/gardb.log" all is fine. If I try starting it as a service (RHEL 9) using the LOG_FILE in the config file, it always encounters "Failed to open '/var/log/gardbd.log' for appending: 2 (no such file or directory" I can find ZERO documentation on what's going on there." This is gardb version 26.4.14.r, installed as part of mariadb-server-galera.

1 0

frm files were deleted, how to recover?
by lkhaajav＠limes.kr 27 Nov '24

27 Nov '24

Hi everybody? Today is the first snow day of the year in Seoul, every thing is white outside, it is a beautiful day. Some of *.frm and *.ibd files were deleted forever accidently. Those cannot be recovered. I used some file-recovery tools but failed. Also data was partitioned. Is there any way to recover *.ibd partitioned files without *.frm ? MariaDB version is 10.7.3. Storage Engine is InnoDB. I tried innodb_force_recovery=6, also created same structure frm files and used discard, import, but partitioned tables cannot be supported for discard and import. Please help me!

1 0

Slow Log Rotation Hang Bug
by Gordan Bobic 19 Nov '24

19 Nov '24

I've been doing some testing with various versions of MySQL and MariaDB regarding slow log rotation. And it looks like MariaDB (tested 10.4, 10.5, 10.6 so far) suffers from a bug. Setup: sloq_query_log=1 long_query_time=0 # sysbench oltp_read_write --threads=$(nproc) Action: mv slow.log slow.log.1 MariaDB [(none)]> flush slow logs; ^^ This never returns (never as in I haven't tried waiting for > 10 minutes). On MySQL 5.5 this is instantaneous. On 5.6 - 8.0 it takes a few seconds, worst case I measured over the weekend is 77s, which is pretty terrible, but with MariaDB 10.3 - 10.6 it never seems to complete at all. If I kill sysbench, it completes immediately. On 10.3 it works, in line with MySQL 5.6 - 8.0. This seems like a rather significant bug.

2 4

MariaDB 10.5 - add replication to existing installation
by Dan O'Reilly 15 Nov '24

15 Nov '24

When I try to add replication to an existing installation, mariadb refuses to start (I'm a novice at MariaDB). This is on RHEL 9. This is my server.cnf: # These groups are read by MariaDB server. # Use it for options that only the server (but not clients) should see # # See the examples of server my.cnf files in /usr/share/mysql/ # # this is read by the standalone daemon and embedded servers [server] # this is only for the mysqld standalone daemon # Settings user and group are ignored when systemd is used. # If you need to run mysqld under a different user or group, # customize your systemd unit file for mysqld/mariadb according to the # instructions in http://fedoraproject.org/wiki/Systemd [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock log-error=/var/log/mariadb/mariadb.log pid-file=/run/mariadb/mariadb.pid # next stuff copied from the original zabbix 5 server.cnf default-storage-engine=innodb innodb_autoinc_lock_mode=2 innodb_buffer_pool_size=1GB innodb_doublewrite=1 innodb_file_per_table=1 innodb_flush_method = O_DIRECT innodb_log_file_size=128M long_query_time=1 max-allowed-packet=16M max_connections=800 max_heap_table_size=256M performance_schema=on query_cache_size=0 query_cache_type=0 slow_query_log=1 slow_query_log_file=/var/lib/mysql/slowlog/mysql-slow.log thread-cache-size=50 tmp_table_size=512M # # * Galera-related settings # [galera] # Mandatory settings #wsrep_on=ON #wsrep_provider= #wsrep_cluster_address= #binlog_format=row #default_storage_engine=InnoDB #innodb_autoinc_lock_mode=2 # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 # # Optional setting #wsrep_slave_threads=1 #innodb_flush_log_at_trx_commit=0 # this is only for embedded server [embedded] # This group is only read by MariaDB servers, not by MySQL. # If you use the same .cnf file for MySQL and MariaDB, # you can put MariaDB-only options here [mariadb] # This group is only read by MariaDB-10.5 servers. # If you use the same .cnf file for MariaDB of different versions, # use this group for options that older servers don't understand [mariadb-10.5] # server-id=1 log_bin = /var/log/mysql/mysql-bin.log log_bin_index =/var/log/mysql/mysql-bin.log.index relay_log = /var/log/mysql/mysql-relay-bin relay_log_index = /var/log/mysql/mysql-relay-bin.index The error I get is: # systemctl status mariadb × mariadb.service - MariaDB 10.5 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; preset: disabled) Active: failed (Result: exit-code) since Mon 2024-11-11 16:31:02 MST; 12min ago Duration: 2h 35min 21.402s Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 426050 ExecStartPre=/usr/libexec/mariadb-check-socket (code=exited, status=0/SUCCESS) Process: 426072 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir mariadb.service (code=exited, status=1/FAILURE) CPU: 281ms Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426111]: the maria-discuss email list at https://launchpad.net/~maria-discuss Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426111]: Please check all of the above before submitting a bug report Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426111]: at https://mariadb.org/jira Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426072]: Initialization of MariaDB database failed. Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426072]: Perhaps /etc/my.cnf is misconfigured or there is some problem with permissions of /var/lib/mysql. Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426072]: Initialization of MariaDB database was not finished successfully. Nov 11 16:31:02 tmv1zbdb01 mariadb-prepare-db-dir[426072]: Files created so far will be removed. Nov 11 16:31:02 tmv1zbdb01 systemd[1]: mariadb.service: Control process exited, code=exited, status=1/FAILURE Nov 11 16:31:02 tmv1zbdb01 systemd[1]: mariadb.service: Failed with result 'exit-code'. Nov 11 16:31:02 tmv1zbdb01 systemd[1]: Failed to start MariaDB 10.5 database server.

3 3

how to backup MyRocks Database without InnoDB Using mariadb-backup
by i18n.site 12 Nov '24

12 Nov '24

I am facing an issue while attempting to back up my MariaDB database, which is entirely based on the MyRocks storage engine. My MariaDB was compiled without InnoDB support, and I am using `mariadb-backup` to perform the backup. However, I encounter the following error: ❯ sudo -u mysql /usr/local/mysql/bin/mariadb-backup --backup --target-dir=/tmp/rebuild_slave [00] 2024-11-13 06:37:55 Connecting to MariaDB server host: localhost, user: mysql, password: not set, port: 2883, socket: /run/mysqld/mysqld.sock [00] 2024-11-13 06:37:56 Using server version 11.4.2-MariaDB-log /usr/local/mysql/bin/mariadb-backup based on MariaDB server 11.4.2-MariaDB Linux (x86_64) [00] 2024-11-13 06:37:56 uses posix_fadvise(). [00] 2024-11-13 06:37:56 cd to /mnt/data/i18n/mariadb/data/ [00] 2024-11-13 06:37:56 open files limit requested 0, set to 108224 [00] 2024-11-13 06:37:56 mariabackup: using the following InnoDB configuration: [00] 2024-11-13 06:37:56 innodb_data_home_dir = . [00] 2024-11-13 06:37:56 innodb_data_file_path = ibdata1:10M:autoextend [00] 2024-11-13 06:37:56 innodb_log_group_home_dir = . 2024-11-13 6:37:56 0 [Note] InnoDB: Number of transaction pools: 1 2024-11-13 6:37:56 0 [ERROR] InnoDB: File ./ib_logfile0 was not found [00] 2024-11-13 06:37:56 Error: cannot read redo log header ❯ sudo -u mysql /usr/local/mysql/bin/mariadb-backup --backup --target-dir=/tmp/rebuild_slave --skip-innodb-backup /usr/local/mysql/bin/mariadb-backup: unknown option '--skip-innodb-backup' ❯ sudo -u mysql /usr/local/mysql/bin/mariadb-backup --backup --target-dir=/tmp/rebuild_slave --rocksdb-backup [00] 2024-11-13 06:38:53 Connecting to MariaDB server host: localhost, user: mysql, password: not set, port: 2883, socket: /run/mysqld/mysqld.sock [00] 2024-11-13 06:38:53 Using server version 11.4.2-MariaDB-log /usr/local/mysql/bin/mariadb-backup based on MariaDB server 11.4.2-MariaDB Linux (x86_64) [00] 2024-11-13 06:38:53 uses posix_fadvise(). [00] 2024-11-13 06:38:53 cd to /mnt/data/i18n/mariadb/data/ [00] 2024-11-13 06:38:53 open files limit requested 0, set to 108224 [00] 2024-11-13 06:38:53 mariabackup: using the following InnoDB configuration: [00] 2024-11-13 06:38:53 innodb_data_home_dir = . [00] 2024-11-13 06:38:53 innodb_data_file_path = ibdata1:10M:autoextend [00] 2024-11-13 06:38:53 innodb_log_group_home_dir = . 2024-11-13 6:38:53 0 [Note] InnoDB: Number of transaction pools: 1 2024-11-13 6:38:53 0 [ERROR] InnoDB: File ./ib_logfile0 was not found [00] 2024-11-13 06:38:53 Error: cannot read redo log header ❯ mariadb-backup -v mariadb-backup based on MariaDB server 11.4.2-MariaDB Linux (x86_64) ────── i18N.Site : MarkDown Translate / Website Solution ( 翻译&建站工具 )

1 0

(no subject)
by i18n.site 12 Nov '24

12 Nov '24

I am facing an issue while attempting to back up my MariaDB database, which is entirely based on the MyRocks storage engine. My MariaDB was compiled without InnoDB support, and I am using `mariadb-backup` to perform the backup. However, I encounter the following error: ❯ sudo -u mysql /usr/local/mysql/bin/mariadb-backup --backup --target-dir=/tmp/rebuild_slave [00] 2024-11-13 06:37:55 Connecting to MariaDB server host: localhost, user: mysql, password: not set, port: 2883, socket: /run/mysqld/mysqld.sock [00] 2024-11-13 06:37:56 Using server version 11.4.2-MariaDB-log /usr/local/mysql/bin/mariadb-backup based on MariaDB server 11.4.2-MariaDB Linux (x86_64) [00] 2024-11-13 06:37:56 uses posix_fadvise(). [00] 2024-11-13 06:37:56 cd to /mnt/data/i18n/mariadb/data/ [00] 2024-11-13 06:37:56 open files limit requested 0, set to 108224 [00] 2024-11-13 06:37:56 mariabackup: using the following InnoDB configuration: [00] 2024-11-13 06:37:56 innodb_data_home_dir = . [00] 2024-11-13 06:37:56 innodb_data_file_path = ibdata1:10M:autoextend [00] 2024-11-13 06:37:56 innodb_log_group_home_dir = . 2024-11-13 6:37:56 0 [Note] InnoDB: Number of transaction pools: 1 2024-11-13 6:37:56 0 [ERROR] InnoDB: File ./ib_logfile0 was not found [00] 2024-11-13 06:37:56 Error: cannot read redo log header ❯ sudo -u mysql /usr/local/mysql/bin/mariadb-backup --backup --target-dir=/tmp/rebuild_slave --skip-innodb-backup /usr/local/mysql/bin/mariadb-backup: unknown option '--skip-innodb-backup' ❯ sudo -u mysql /usr/local/mysql/bin/mariadb-backup --backup --target-dir=/tmp/rebuild_slave --rocksdb-backup [00] 2024-11-13 06:38:53 Connecting to MariaDB server host: localhost, user: mysql, password: not set, port: 2883, socket: /run/mysqld/mysqld.sock [00] 2024-11-13 06:38:53 Using server version 11.4.2-MariaDB-log /usr/local/mysql/bin/mariadb-backup based on MariaDB server 11.4.2-MariaDB Linux (x86_64) [00] 2024-11-13 06:38:53 uses posix_fadvise(). [00] 2024-11-13 06:38:53 cd to /mnt/data/i18n/mariadb/data/ [00] 2024-11-13 06:38:53 open files limit requested 0, set to 108224 [00] 2024-11-13 06:38:53 mariabackup: using the following InnoDB configuration: [00] 2024-11-13 06:38:53 innodb_data_home_dir = . [00] 2024-11-13 06:38:53 innodb_data_file_path = ibdata1:10M:autoextend [00] 2024-11-13 06:38:53 innodb_log_group_home_dir = . 2024-11-13 6:38:53 0 [Note] InnoDB: Number of transaction pools: 1 2024-11-13 6:38:53 0 [ERROR] InnoDB: File ./ib_logfile0 was not found [00] 2024-11-13 06:38:53 Error: cannot read redo log header ❯ mariadb-backup -v mariadb-backup based on MariaDB server 11.4.2-MariaDB Linux (x86_64) ────── i18N.Site : MarkDown Translate / Website Solution ( 翻译&建站工具 )

1 0

Monitoring mariaDB through SNMP
by Noah 04 Nov '24

04 Nov '24

Ahoy List Members, I hope you are well. Is there a good guide that explains how to set up monitoring mariaDB via SNMP? Cheers, Noah

3 2

Migrate MySQL5.7 to MariaDB 10.4, then to MariaDB 10.11 Failed
by edwin.chan＠checkit.net 30 Oct '24

30 Oct '24

Hi, I am going to migrate our existing MySQL5.7 to MariaDB 10.11.9. I setup a new Windows server that installed MySQL 5.7, MariaDB 10.4.34 and MariaDB 10.11.9 without create a new instance. I copied the data directory of MySQL5.7 from existing Windows server to the new server for migration test. First, I am able to start the MySQL5.7 on the new server. Then, I upgrade the MySQL5.7 to MariaDB 10.4.34 successfully using mysql_upgrade_service.exe which under MariaDB 10.4.34 bin directory. But failed at the last step that upgrade MariaDB 10.4.34 to MariaDB 10.11.9 using mariadb-upgrade-service.exe which under MariaDB 10.11.9 bin directory. From the error log, got below message 2024-10-03 16:17:39 0 [Note] InnoDB: Buffer pool(s) load completed at 241003 16:17:39 241003 16:17:40 [ERROR] mysqld got exception 0xc0000005 ; Sorry, we probably made a mistake, and this is a bug. Your assistance in bug reporting will enable us to fix this for the next release. To report this bug, see https://mariadb.com/kb/en/reporting-bugs From the upgrade log, got below message Phase 3/8: Running 'mysql_fix_privilege_tables' ERROR 2017 (HY000): Can't open named pipe to host: . pipe: mysql_upgrade_service_3564 (2) FATAL ERROR: Upgrade failed Checked named pipe enabled and local client able to connect using named pipe at each stage. Any idea why upgrade failed? When upgrade, MariaDB start the instance with socket which is not same as the socket option in my.ini. In this case, it start with socket mysql_upgrade_service_3564; I tried few times the last 4 numeric digits are not fixed and change every time. Thanks.

5 6

Logging options to debug SSL problem
by Andrew Wood 14 Oct '24

14 Oct '24

Hi Is there a way to get the server to log verbosely everything to do with connection attempts in order to try and debug why a client keeps getting error 2026 SSL connection error: socket layer receive error? There is currently nothing being logged on the server other than: [Warning] Aborted connection 332 to db: 'unconnected' user: 'unauthenticated' host: '192.168.253.231' (This connection closed normally without authentication) SHOW GLOBAL VARIABLES LIKE 'tls_version'; gives TLSv1.1,TLSv1.2,TLSv1.3 and the client is based on a relatively recent version of libmysqlclient so Im struggling to understand what is going wrong without some more detailed logging. Thanks Andrew

3 3

Performance questions after Migrating from MariaDB 5.5.68 to 10.11.6 (and 9)
by cyusedfzfb 10 Oct '24

10 Oct '24

Dear MariaDB List Readers, I hope formatting will survive...i tried to make this as readable as possible. Due to our ongoing migration from RHEL7 to RHEL9, we are also upgrading some databases from MariaDB 5.5.68 (on RHEL7) to MariaDB 10.11.6 (on RHEL9). During this process, we've noticed a significant performance drop, particularly with UPDATE and DELETE operations. To investigate this further and rule out external factors, I created a single RHEL9 VM and downloaded both the x86_64/systemd versions of MariaDB 5.5.68 and 10.11.9 from MariaDB Downloads. (https://mariadb.org/download) I installed both versions on the same VirtualBox VM, using default configurations, and placed them on the same partition (/usr/local). I followed the installation instructions in the INSTALL-BINARY file. I then ran a benchmark on both versions using a variation of this PHP benchmark script: https://github.com/sergix44/php-benchmark-script. Here are the results: *MariaDB 5.5.68*: Server version: 5.5.68-MariaDB MariaDB Server mysql::ping,0.0002 mysql::select_version,0.1299 mysql::select_all,0.6270 mysql::select_cursor,0.8542 mysql::seq_insert,2.0182 mysql::bulk_insert,0.0204 mysql::update,0.0005 mysql::update_with_index,0.0005 mysql::transaction_insert,0.0014 mysql::indexes,0.0000 mysql::delete,0.0005 mysql::select_version::q/s,15403 mysql::select_all::q/s,3190 mysql::seq_insert::q/s,991 mysql::update::q/s,3895386 mysql::update_with_index::q/s,4105436 mysql::transaction_insert::t/s,1460821 mysql::delete::q/s,4436065 Total time: 13.2027 s Peak memory usage: 23.82 MiB *MariaDB 10.11.9*: Server version: 10.11.9-MariaDB MariaDB Server mysql::ping,0.0001 mysql::select_version,0.1268 mysql::select_all,0.6435 mysql::select_cursor,0.8352 mysql::seq_insert,2.2696 mysql::bulk_insert,0.6556 mysql::update,1.4104 mysql::update_with_index,0.3981 mysql::transaction_insert,2.5425 mysql::indexes,0.2353 mysql::delete,2.2246 mysql::select_version::q/s,15772 mysql::select_all::q/s,3108 mysql::seq_insert::q/s,881 mysql::update::q/s,1418 mysql::update_with_index::q/s,8963 mysql::transaction_insert::t/s,787 mysql::delete::q/s,899 Total time: 20.9426 s Peak memory usage: 23.82 MiB The key observations: - **UPDATE performance:** - 5.5.68: *3,895,386* q/s - 10.11.9: *1,418* q/s - **UPDATE with index:** - 5.5.68: *4,105,436* q/s - 10.11.9: *8,963* q/s - **DELETE performance:** - 5.5.68: *4,436,065* q/s - 10.11.9: *899* q/s I also tested MariaDB 10.11.6, and the results were similar to 10.11.9. Our web application feels noticeably slower, and the benchmark results seem to confirm this. Is this drastic performance drop expected with newer MariaDB versions? While we are aware of tuning options (like `innodb_buffer_pool_size`, file system mount options, `innodb_flush_log_at_trx_commit`, etc.), both versions were run with default settings and no tuning. How can it be that MariaDB 5.5.68 is performing several orders of magnitude faster than 10.11.x for these specific operations? Best regards, MJ To end, and to be complete: find below the actual script used to create the stats: <?php $initialRowCount = 1000; $mysqli = null; setup(function ($args) use (&$mysqli, $initialRowCount) { if (!extension_loaded('mysqli')) { print('The mysqli extension is not loaded' . PHP_EOL); return; } if ($args['mysql_host'] === null || $args['mysql_user'] === null || $args['mysql_password'] === null) { print('The --mysql_host=, --mysql_user=, and --mysql_password= arguments are required' . PHP_EOL); return; } $mysqli = new mysqli($args['mysql_host'], $args['mysql_user'], $args['mysql_password'], null, isset($args['mysql_port']) ? $args['mysql_port'] : 3306); if ($mysqli->connect_error) { printf("Mysql Connect Error (%s) %s\n", $mysqli->connect_errno, $mysqli->connect_error); return; } // drop database $mysqli->query("DROP DATABASE IF EXISTS `bench_test`"); // create database $mysqli->query("CREATE DATABASE IF NOT EXISTS `bench_test`"); $mysqli->select_db('bench_test'); $mysqli->query("CREATE TABLE IF NOT EXISTS `bench_test`.`test` (id INT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(255))"); for ($i = 0; $i < $initialRowCount; $i++) { $values[] = "('test$i')"; } $mysqli->query("INSERT INTO `bench_test`.`test` (name) VALUES " . implode(',', $values)); }); teardown(function () use (&$mysqli) { if ($mysqli === null) { return; } $mysqli->query("DROP DATABASE IF EXISTS `bench_test`"); $mysqli->close(); }); return [ 'ping' => function () use (&$mysqli) { if ($mysqli === null) { return INF; } $mysqli->ping(); return 1; }, 'select_version' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->query("SELECT VERSION()"); } extraStat('q/s', round($count / (StopWatch::time() - $time))); return $i; }, 'select_all' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->query("SELECT * FROM `bench_test`.`test`"); } extraStat('q/s', round($count / (StopWatch::time() - $time))); return $i; }, 'select_cursor' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; for ($i = 0; $i < $count; $i++) { $result = $mysqli->query("SELECT * FROM `bench_test`.`test`"); while ($row = $result->fetch_assoc()) { } $result->close(); } return $i; }, 'seq_insert' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->query("INSERT INTO `bench_test`.`test` (name) VALUES ('test')"); } extraStat('q/s', round($count / (StopWatch::time() - $time))); return $i; }, 'bulk_insert' => function ($multiplier = 1, $count = 100000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $values = []; for ($i = 0; $i < $count; $i++) { $values[] = "('test$i')"; } $mysqli->query("INSERT INTO `bench_test`.`test` (name) VALUES " . implode(',', $values)); return $i; }, 'update' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->query("UPDATE `bench_test`.`test` SET name = 'test' WHERE id = '$i'"); } extraStat('q/s', round($count / (StopWatch::time() - $time))); return $i; }, 'update_with_index' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $mysqli->query("CREATE INDEX idx ON `bench_test`.`test` (id)"); $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->query("UPDATE `bench_test`.`test` SET name = 'test' WHERE id = '$i'"); } extraStat('q/s', round($count / (StopWatch::time() - $time))); $mysqli->query("DROP INDEX idx ON `bench_test`.`test`"); return $i; }, 'transaction_insert' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->begin_transaction(); $mysqli->query("INSERT INTO `bench_test`.`test` (name) VALUES ('test')"); $mysqli->commit(); } extraStat('t/s', round($count / (StopWatch::time() - $time))); return $i; }, 'indexes' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $mysqli->query("CREATE INDEX idx_name ON `bench_test`.`test` (name)"); $mysqli->query("DROP INDEX idx_name ON `bench_test`.`test`"); return 1; }, 'delete' => function ($multiplier = 1, $count = 1000) use (&$mysqli) { if ($mysqli === null) { return INF; } $count = $count * $multiplier; $time = StopWatch::time(); for ($i = 0; $i < $count; $i++) { $mysqli->query("DELETE FROM `bench_test`.`test` WHERE id = '$i'"); } extraStat('q/s', round($count / (StopWatch::time() - $time))); return $i; }, ];

5 9

mariadb 10.6.17 + galera-26.4.19
by Jaco Kroon 07 Oct '24

07 Oct '24

Hi, We're observing the following crash using galera and mariadb versions as per subject. Usually only one of the three nodes will go down, but last night two went down within minutes of each other resulting in a fairly nasty outage. Given the frequency of these crashes (about one once a month) I highly suspect we're doing something wrong causing us to run into this, but not others. So any advise appreciated. Stack trace as per logs: 241007 1:01:25 [ERROR] mysqld got signal 11 ; Sorry, we probably made a mistake, and this is a bug. Your assistance in bug reporting will enable us to fix this for the next release. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.6.17-MariaDB-log source revision: 15c75ad083a55e198ae78324f22970694b72f22b key_buffer_size=536870912 read_buffer_size=1048576 max_used_connections=522 max_threads=10002 thread_count=83 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10498887186 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f675c000c68 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x7f7f78056da8 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x32)[0x5632cb5f2212] /usr/sbin/mysqld(handle_fatal_signal+0x2b3)[0x5632cb133db3] /lib64/libc.so.6(+0x3c760)[0x7f7f7b653760] /usr/sbin/mysqld(+0x8ee692)[0x5632cb44b692] /usr/sbin/mysqld(+0x8ef5cd)[0x5632cb44c5cd] /usr/sbin/mysqld(+0x8acfa5)[0x5632cb409fa5] /usr/sbin/mysqld(+0x24e630)[0x5632cadab630] /usr/sbin/mysqld(+0x24e6b5)[0x5632cadab6b5] /usr/sbin/mysqld(+0x949418)[0x5632cb4a6418] /usr/sbin/mysqld(+0x960b34)[0x5632cb4bdb34] /usr/sbin/mysqld(+0x8b9e7c)[0x5632cb416e7c] /usr/sbin/mysqld(_ZN7handler10ha_rnd_posEPhS0_+0x232)[0x5632cb13b022] /usr/sbin/mysqld(_ZN14Rows_log_event8find_rowEP14rpl_group_info+0x3e4)[0x5632cb2624c4] /usr/sbin/mysqld(_ZN21Delete_rows_log_event11do_exec_rowEP14rpl_group_info+0x142)[0x5632cb2629b2] /usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0x35f)[0x5632cb255c9f] /usr/sbin/mysqld(_Z18wsrep_apply_eventsP3THDP14Relay_log_infoPKvm+0x1fd)[0x5632cb3def8d] /usr/sbin/mysqld(+0x868ff0)[0x5632cb3c5ff0] /usr/sbin/mysqld(_ZN21Wsrep_applier_service15apply_write_setERKN5wsrep7ws_metaERKNS0_12const_bufferERNS0_14mutable_bufferE+0xb5)[0x5632cb3c6ba5] /usr/sbin/mysqld(+0xb0c921)[0x5632cb669921] /usr/sbin/mysqld(+0xb1dfd6)[0x5632cb67afd6] /usr/lib64/galera/libgalera_smm.so(+0x60724)[0x7f7f7b260724] /usr/lib64/galera/libgalera_smm.so(+0x6fa67)[0x7f7f7b26fa67] /usr/lib64/galera/libgalera_smm.so(+0x74d65)[0x7f7f7b274d65] /usr/lib64/galera/libgalera_smm.so(+0x9fdc3)[0x7f7f7b29fdc3] /usr/lib64/galera/libgalera_smm.so(+0xa098e)[0x7f7f7b2a098e] /usr/lib64/galera/libgalera_smm.so(+0x75200)[0x7f7f7b275200] /usr/lib64/galera/libgalera_smm.so(+0x4f35f)[0x7f7f7b24f35f] /usr/sbin/mysqld(_ZN5wsrep18wsrep_provider_v2611run_applierEPNS_21high_priority_serviceE+0x12)[0x5632cb67b652] /usr/sbin/mysqld(+0x8842d1)[0x5632cb3e12d1] /usr/sbin/mysqld(_Z15start_wsrep_THDPv+0x276)[0x5632cb3d0d16] /usr/sbin/mysqld(+0x80e941)[0x5632cb36b941] /lib64/libc.so.6(+0x8ad22)[0x7f7f7b6a1d22] /lib64/libc.so.6(+0x10698c)[0x7f7f7b71d98c] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f7efdea05db): delete from `jobs` where `id` = 808933436 Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=off,cset_narrowing=off The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /var/lib/mysql Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 1031460 1031460 processes Max open files 91983 91983 files Max locked memory 8388608 8388608 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 1031460 1031460 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: core Kernel version: Linux version 6.4.12-uls (root@sysrescue) (gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826, GNU ld (Gentoo 2.41 p2) 2.41.0) #2 SMP PREEMPT_DYNAMIC Thu Jan 4 20:10:49 SAST 2024 I'm unable to locate the referenced core file or I'd already have pulled that into gdb. Any advise or pointers appreciated. I do notice there are galera updates, and a number of mariadb upgrades available. For galera this looks like improvements in logging, so probably not the cause of the crash, and for mariadb in 10.6.18 these items stand out for me: Server crashes in JOIN_CACHE::write_record_data upon EXPLAIN with subqueries and constant tables (MDEV-21102 <https://jira.mariadb.org/browse/MDEV-21102>) - but the stack trace doesn't match. Server crash in Rows_log_event::update_sequence upon replaying binary log (MDEV-31779 <https://jira.mariadb.org/browse/MDEV-31779>) - this looks feasible. If anyone can confirm my conjecture that would be great. We'd want to test 10.11 or even 11.4 in a non-production environment before making a big jump to one of those versions in production. Kind regards, Jaco

1 0

mysql_native_password authentication plugin
by cyusedfzfb 06 Oct '24

06 Oct '24

Hi, Just a quick question: we understand that mysql_native_password authentication plugin has become deprecated, and yes: we are in the process of moving to caching_sha2_password. We read everywhere that mysql_native_password is "subject to removal in a future version of MySQL" Can anyone say how soon that removal is going to be? (as for now it seems just a change of the default authentication mechanism, and I cannot find a date/year/version for *actual* removal) (and yes I did google) :-) Thanks!

3 2

Cannot backup database
by Marc Chamberlin 06 Oct '24

06 Oct '24

Hello - I am wanting to backup my databases and until now I haven't experienced any difficulties. I am working on an OpenSuSE 15.4 system and wanting to upgrade it which is why I want to backup the databases first. The version of mariadb is : > >> quasar:/srv/mysql #mariadb -V >> mariadb Ver 15.1 Distrib 10.6.15-MariaDB, for Linux (x86_64) using >> EditLine wrapper >> > But now I am hitting a new snag, when I try to run the backup script I > get the following response - > >> quasar:/srv/mysql #./mysqlbackup.sh >> mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ >> `EVENT_CATALOG`, `EVENT_SCHEMA`, `EVENT_NAME`, `DEFINER`, >> `TIME_ZONE`, `EVENT_BODY`, `EVENT_DEFINIT >> ION`, `EVENT_TYPE`, `EXECUTE_AT`, `INTERVAL_VALUE`, `INTERVAL_FIELD`, >> `SQL_MODE`, `STARTS`, `ENDS`, `STATUS`, `ON_COMPLETION`, `CREATED`, >> `LAST_ALTERED`, `LAST_ >> EXECUTED`, `EVENT_COMMENT`, `ORIGINATOR`, `CHARACTER_SET_CLIENT`, >> `COLLATION_CONNECTION`, `DATABASE_COLLATION` FROM `EVENTS`': Cannot >> proceed, because event sch >> eduler is disabled (1577) >> > The mysql.log file is showing these 2 error messages also - > >> 2024-10-05 14:43:30 0 [ERROR] Incorrect definition of table >> mysql.event: expected column 'definer' at position 3 to have type >> varchar(, found type char(141). >> 2024-10-05 14:43:30 0 [ERROR] mysqld: Event Scheduler: An error >> occurred when initializing system tables. Disabling the Event Scheduler. > My Duck Duck Go searches on the internet suggested I put the following > line in the file my.cnf > >> event_scheduler=ON > but no joy. Also, most of my internet searches hit on solutions that > were designed for running mariadb in a docker container. I am NOT > using docker, don't even know how to, and don't want solutions that > require docker. Too much to try an grok at this time for me. > > One interesting item of note is that on OpenSuSE (at least) the > systemd file mariadb.service runs both the install and the upgrade > services before starting the actual mysql daemon. Here is an excerpt > from mariadb.service that shows this - > >> [Service] >> ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install >> ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade >> ExecStart=/usr/lib/mysql/mysql-systemd-helper start > Anyone got any bright and wonderful ideas on how to make mariadb a > happy camper that will allow me to do a database backup? > > Many thanks in advance for those who can guide me back to the mariadb > light! Marc C... > >

2 1

Re: Migrate MySQL5.7 to MariaDB 10.4, then to MariaDB 10.11 Failed
by Edwin Chan 04 Oct '24

04 Oct '24

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

Re: Migrate MySQL5.7 to MariaDB 10.4, then to MariaDB 10.11 Failed
by Edwin Chan 04 Oct '24

04 Oct '24

Hi Marko, Attached the mysqld.dmp. Thanks. Regards, Edwin Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

unexpected swap usage for mysqld (but mariadb) process
by cyusedfzfb 29 Sep '24

29 Sep '24

Hi all! New here, signed up just new, to discuss an interesting mariadb behaviour we are seeing, related to mariadb unexpectedly using swap space. Look at this example: RHEL 8.10, running mariadb-server-utils.x86_64 3:10.5.22-1.module+el8.8.0+20134+a92c7654: > [user@db ~]$ free -g > total used free shared buff/cache > available > Mem: 187 9 11 0 165 175 > Swap: 3 3 0 and: > top - 08:52:46 up 39 days, 15:50, 2 users, load average: 1.70, 2.05, > 1.99 > Tasks: 616 total, 2 running, 614 sleeping, 0 stopped, 0 zombie > %Cpu(s): 6.0 us, 0.8 sy, 0.0 ni, 88.2 id, 4.7 wa, 0.1 hi, 0.1 > si, 0.0 st > MiB Mem : 191529.7 total, 11761.7 free, 9764.9 used, 170003.1 > buff/cache > MiB Swap: 4096.0 total, 1006.1 free, 3089.9 used. 179429.5 avail > Mem > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > COMMAND *SWAP * > 1952811 mysql 20 0 14.4g 5.0g 15172 S 65.7 2.7 9663:14 > mysqld* 1.7g * > 2934963 root 20 0 5208 2056 1408 S 8.9 0.0 10:39.29 > gzip 0 > 2934962 root 20 0 33612 8268 6960 S 7.9 0.0 2:35.31 > mysqldump 0 while: > [user@db ~]$ cat /proc/sys/vm/swappiness > 1 We could (we should..) allocate more ram to mariadb, but the point is: there is plenty of RAM available, and there always has been, since boot. And yet, mariadb is using all swap. I guess this has no performance impact, probably the swapped pages are not actually used, but zabbix does not like 100% swap usage. And frankly: neither do I. Why? Can anyone here explain? Swappiness set to 1...is mariadb ignoring swappiness..? Is there something else we can configure..? I read some older posts on ram/swap, and here is some data, requested in that older thread: > [user@db ~]$ sudo ps -o pid,vsz,comm `pgrep mysqld` > PID VSZ COMMAND > 1952811 15117612 mysqld and > [user@db ~]$ for file in /proc/*/status ; do awk > '/VmSwap|Name/{printf $2 " " $3}END{ > > print ""}' $file; done | sort -k 2 -n -r | grep mysql > mysqld 1982672 kB We are seeing similar behaviour on another machines, running more recent mariadb version: 10.5.22-MariaDB MariaDB Server: > [user@db_another ~]$ free -g > total used free shared buff/cache > available > Mem: 62 40 0 1 21 20 > Swap: 4 3 1 Again: enough RAM available, and swap is used 3/4, mostly by MariaDB. Hope the provided information is enough. Let me know if there is anything else I can provide. Looking forward for any insight or help on the matter. :-) Thanks! MJ

5 7

InnoDB database corrupt after unplaned server restart
by Rainer Dorsch 22 Sep '24

22 Sep '24

Hello, I am using mariadb as backend for nextcloud. After an unplanned server restart by my provider I see in the log this error message repeating many times: Sep 21 23:14:06 contabo.bokomoko.de mariadbd[267649]: 2024-09-21 23:14:06 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/ kb/en/library/innodb-recovery-modes/ for information about forcing recovery. Sep 21 23:14:06 contabo.bokomoko.de mariadbd[267649]: 2024-09-21 23:14:06 0 [ERROR] InnoDB: Page [page id: space=0, page number=300] log sequence number 572290405174 is in the future! Current system log sequence number 572290220157. I have a backup of /var/lib/mysql from before the issue. The files which are currently in /var/lib/mysql seem to be stuck with a timestamp from immediately after the reboot. Can anybody advise on a good recovery strategy? Any hint or advice is welcome. Many thanks Rainer -- Rainer Dorsch http://bokomoko.de/

1 0

Database schema error while upgrading Koha 24.05 in Ubuntu 24.04 Noble LTS
by Md Monirul Islam Ansari 20 Sep '24

20 Sep '24

Dear folks, Greetings from Monirul this side, During an upgrade of Koha to version 24.05.03-1, the process failed due to a database access error. The upgrade script was unable to connect to the MySQL/MariaDB database, suggesting a potential issue with database permissions or configuration. Steps to Reproduce: Attempt to upgrade Koha-common package to version 24.05.03-1 Run sudo apt-get install mariadb-server Confirm the installation/upgrade process Observed Behavior: The upgrade process fails during the database schema upgrade step An error message indicates that access is denied for the Koha database user Error Message: "DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_monirul;host=localhost;port=3306','koha_monirul',...) failed: Access denied for user 'koha_monirul'@'localhost' (using password: YES) at /usr/share/koha/lib/Koha/Database.pm line 91. at /usr/share/koha/lib/Koha/Database.pm line 139" Environment: Koha version being upgraded to: 24.05.03-1 Database: MariaDB (version 1:10.11.8-0ubuntu0.24.04.1) Operating System: Ubuntu (likely 24.04 based on package versions)

2 1

Joining two tables on a list of values
by Gingko 14 Sep '24

14 Sep '24

Hello, I would like to know if is there some (efficient!) way to join two tables on a list of values contained in (likely a single column) of the joined table, whatever form could have this list of values ? For example, I have a main table containing: main_table: +------------+------------------+------+-----+------------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------+------------------+------+-----+------------+----------------+ | index | int(11) | NO | PRI | 0 | | | to_join | int(11) | NO | | 0 | | | <other fields, irrelevant> | | || | +------------+------------------+------+-----+------------+----------------+ … and a secondary table containing: joined_table: +------------+------------------+------+-----+------------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------+------------------+------+-----+------------+----------------+ | index | int(11) | NO | PRI | | auto_increment | | int_list | <list_of_ints> | YES | | (empty) | | | <other fields, irrelevant> | | | | | +------------+------------------+------+-----+------------+----------------+ We could suppose, here, as a simple test case, that main_table has five rows where to_join contains respectively 1, 2, 3, 4, and 5, and the joined_table has a single row with the single column int_list combining 2 and 4 in any form (but of course, this list could actually have any length). I'd like to join these tables using a statement like: SELECT <anything> FROM main_table AS M LEFT JOIN joined_table AS J ON M.to_join <some_operator to> J.int_list; … in such a way that main_table would be joined to joined_table using any value contained in int_list, and the statement is expected to give two rows as a result. I tried to set int_list as a TINYTEXT containing "2,4" and use: SELECT <anything> FROM main_table AS M LEFT JOIN joined_table AS J ON M.to_join IN (J.int_list); … but this doesn't work, of course, my comma separated list is seen as a whole single value. I also tried, still using TINYTEXT, the list as "[2][4]" and use: SELECT <anything> FROM main_table AS M LEFT JOIN joined_table AS J ON J.int_listLIKE CONCAT('%[', M.to_join , ']%'); This works (more or less), but it is excruciatingly slow, especially knowing that main_table can actually contain millions of rows, and joined_table several thousands. Is there a better solution for doing that? As the final goal implies, somewhere later, associating to_join in main_table, via int_list, to the index auto increment primary key of the joined_table, using multiple rows there is not an option. Regards, Gingko

5 5

Fulltext index tokenization rules / DOC_ID
by wknauf＠hg-online.de 14 Sep '24

14 Sep '24

Hi all, first question: is there a document that describes the rules how MariaDB builds the fulltext index words? I set "innodb_ft_min_token_size=1" to include also one letter words in the index. But this does not seem to work for words like "D'Artagnan": the "d" letter is not found in "information_schema.INNODB_FT_INDEX_TABLE". It works for "D Artagnan". So I assume that single letters that are followed by a quote are ignored when building the index? You could also post the link to the source code file, but I don't know whether my C knowledge is sufficient ;-) Second question: the doc (https://mariadb.com/kb/en/information-schema-innodb_ft_index_table-table/) states that "information_schema.INNODB_FT_INDEX_TABLE.doc_id" matches to the id column of the original table: "DOC_ID: Document ID of the newly added row, either an appropriate ID column or an internal InnoDB value." But this did not happen for me - the doc_id values do not match my ID column. I tried the datatypes "int" and "bigint". Best regards Wolfgang

4 4

MariaDB ServerFest in Berlin on September 17
by Kristian Nielsen 26 Aug '24

26 Aug '24

The next MariaDB ServerFest will take place in Berlin, Germany. The event is on September 17, 2024, and is generously hosted by MariaDB Foundation sponsor Ionos: https://mariadb.org/fest-2024-berlin/ The event is open to all. I was at the MariaDB ServerFest in Helsinki last Autumn, and I really liked the close interaction with the many interesting participants: big and advanced users, developers, university students, service providers, etc. It is an excellent opportunity to meet many of the core developers, and hopefully a lot of other great people! I will be presenting at the event myself; my talk is titled: "MariaDB Replication – Fantastically Flexible and Fragile". I very much welcome questions during my talks, so feel free to prepare questions for me about anything replication. - Kristian.

2 1

MariaDB server crash status=11/SEGV on version 10.6.19
by zxc072211＠gmail.com 21 Aug '24

21 Aug '24

Hi, First, I apologize if my English isn't perfect. After upgrading my MariaDB server from version 10.6.18 to 10.6.19. I encountered an issue. When I execute a "SELECT ... FROM ( SELECT ... ) x WHERE x.colume1 .." statement, the server returns the error: "ERROR 2013 (HY000): Lost connection to server during query." I checked the `/var/log/messages` and found this message: "mariadb.service: Main process exited, code=killed, status=11/SEGV.". I used core dumping to investigate further and found that the stack frame count reaches #12171. The error at #0 is "... Item::build_clone ... at /usr/src/debug/MariaDB-/src_0/sql/item.h:1928". The previous stack frames keep repeating two frames: #1 Item_func_case_simple::do_build_clone ... at /usr/src/debug/MariaDB-/src_0/sql/item_cmpfunc.h:2448 #2 ... Item::build_clone ... at /usr/src/debug/MariaDB-/src_0/sql/item.h:1928 My OS is Rocky Linux 8.10. The MariaDB server versions where I encountered this issue are 10.6.19 and 10.11.9. The MariaDB server version without issues is 10.6.18. Has anyone else encountered this problem? Thanks in advance for any help.

2 2

External MyISAM partitions
by Jan Křístek 07 Aug '24

07 Aug '24

Hi, We have an old instance of MariaDB 10.3.9/10.3.39, with historical data. Every month I copy an old MyISAM partition (binary files) from the same version of the engine (but a different instance) to a big volume and replace an empty partition in the database with symlinks to the newly copied two files (MYD, MYI - when the engine is stopped). I have been doing it for a year or two, checking each time the data are accessible afterwards. This month it happened, that the data are not accessible anymore, and the database throwing an exception: *Got error 140: "Wrong create options" from storage engine MyISAM.* I tried doing it in a new instance, each time I replace a partition with a link to file elsewhere, the error appeared again. Does anyone have any ideas, why it's showing the error and how to avoid it? I cannot recall changing anything in the database configuration, upgrading any database, or doing any other changes. Thanks for any help you can provide, Jan

4 7

Query Performance Drops 10.3 -> 10.5 - Query Optimizer Refusing Index
by Michael Caplan 02 Aug '24

02 Aug '24

HI there, Looking for some advice. A common query "structure" that performed well in 10.3 is showing a significant performance decrease in 10.5.24. The root cause seems to be 10.5's refusal to use a key. The table in question is has a "key => value" like structure: CREATE TABLE `cases_meta` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `case_id` int(10) unsigned NOT NULL, `key` varchar(50) NOT NULL, `value` mediumtext DEFAULT NULL, PRIMARY KEY (`id`), KEY `key` (`key`), KEY `fk_caes_meta_1` (`case_id`), CONSTRAINT `fk_caes_meta_1` FOREIGN KEY (`case_id`) REFERENCES `cases` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci The query in question simply is looking for a `key` with a specific value: SELECT * FROM cases_meta AS cm WHERE cm.`key` = 'PAN_NUMBER' AND cm.`value` = '153566' In this example, the table has 2.8 million records. In 10.5, it skips the `key` key, and grinds through 2.8 million records: ANALYZE: { "query_block": { "select_id": 1, "r_loops": 1, "r_total_time_ms": 2743.92693, "table": { "table_name": "cm", "access_type": "ALL", "possible_keys": ["key"], "r_loops": 1, "rows": 1004130, "r_rows": 2820048, "r_table_time_ms": 2548.916341, "r_other_time_ms": 195.0068087, "filtered": 30.31918144, "r_filtered": 0, "attached_condition": "ddx_lab_801615.cm.`key` = 'PAN_NUMBER' and ddx_lab_801615.cm.`value` = '153566'" } } } In 10.3, it uses the `key` key, and reads through a radically smaller subset of tables to fetch the result: ANALYZE: { "query_block": { "select_id": 1, "r_loops": 1, "r_total_time_ms": 357.84, "table": { "table_name": "cm", "access_type": "ref", "possible_keys": ["key"], "key": "key", "key_length": "152", "used_key_parts": ["key"], "ref": ["const"], "r_loops": 1, "rows": 304484, "r_rows": 155123, "r_total_time_ms": 340.94, "filtered": 100, "r_filtered": 0, "index_condition": "ddx_lab_801615.cm.`key` = 'PAN_NUMBER'", "attached_condition": "ddx_lab_801615.cm.`value` = '153566'" } } } I'm not sure why 10.5 is taking this substandard approach. Adding a USE INDEX (`key`) seems to have no effect in 10.5 either, it just skips the index. Any ideas? Thanks, Mike Confidentiality Notice: The information contained in this electronic message and any attachments to this message are intended only for the individual(s) addressed in the message and may contain proprietary and confidential information. If you are not the intended recipient, you should not disseminate, distribute, or copy this e-mail. Please notify the sender and destroy this message. WARNING: Computer viruses can be transmitted via email. The recipient should scan this email before opening it. The company accepts no liability for any damage caused by any virus transmitted by this email. Confidentiality Notice: The information contained in this electronic message and any attachments to this message are intended only for the individual(s) addressed in the message and may contain proprietary and confidential information. If you are not the intended recipient, you should not disseminate, distribute, or copy this e-mail. Please notify the sender and destroy this message. WARNING: Computer viruses can be transmitted via email. The recipient should scan this email before opening it. The company accepts no liability for any damage caused by any virus transmitted by this email.

2 3

mariadb connector/c client not using SSL
by Chris Ross (cross2) 30 Jul '24

30 Jul '24

Hey there. I am trying to get a local application which uses the mariadb client library to connect to a server with SSL. On my client system, I have added “ssl-ca” and “ssl-verify-server-cert” to the [client] section of my my.cnf. I can see these in effect with both “mariadb --help” and with “my_print_defaults client”. And, using mariadb client itself with all of the right connection parameters (host/port/username/port/schema) it connects just fine. However, a program of mine which uses mysql_real_connect() fails, reporting “Access denied for user ‘foo’@’ip’ (using password: YES)”. This is, I assume, because the user on the database side requires ssl, and my client is not using ssl. I’ve added: (void)mysql_optionsv(conn, MYSQL_READ_DEFAULT_FILE, NULL); Into my sources before calling mysql_real_connect(). I thought that would make it pull the params from the config file, and all should be good. But, that’s clearly not enough. Can someone help me figure out what I’m missing? Thank you. * Chris

3 10

insert multiple SET type values in prepared statement?
by J.D. 28 Jul '24

28 Jul '24

Trying to insert multiple values of a SET type column using (MariaDB) prepared statements, but keep running into "Data truncated for column <columnN>" no matter how the multi-value string is formatted. Processing is done using PHP-8.2. ... INSERT INTO <table> SET ....<columnN=?> ....; $BindValuesArray[<columnN>]="'value1,value2,value3'"; $BindVarsArray[]=&${$<columnN>}; $BindParamTypes.="s"; ... extract($BindValuesArray); So, trying to insert a (multi-valued) "list string" into a SET type column.

1 0

Poor fulltext index performance in conjunction with order by.
by gava100＠gmail.com 26 Jul '24

26 Jul '24

Hello All, I'm looking for a way to improve a query using fulltext index and so far, couldn't find any good solution. I have an alert table (described below) with around 6 million records and a full-text index on these two columns (ALERT_COMMENT, ALERT_SOURCE). I'd like to query the latest 30 received alerts based on a string content. Currently, I am proceeding with the following query: SELECT * FROM Alert WHERE MATCH(ALERT_COMMENT, ALERT_SOURCE) AGAINST ('string content' IN BOOLEAN MODE) > 0.0 ORDER BY ALERT_ID DESC LIMIT 30; However, this query is taking minutes to retrieve the data, likely due to poor performance of the full-text index in conjunction with the ORDER BY statement. When I remove the 'ORDER BY' statement, the result is returned in seconds. Do you have any suggestions for improving the retrieval time for this query? Below is the table structure: CREATE TABLE `Alert` ( `ALERT_ID` int(11) NOT NULL AUTO_INCREMENT, `SITE_ID` varchar(50) NOT NULL, `ALERT_LEVEL` int(4) NOT NULL, `RECEIVED_TIME` datetime NOT NULL, `OCCURRED_TIME` datetime NOT NULL, `ALERT_SOURCE` varchar(50) NOT NULL, `ALERT_COMMENT` varchar(1024) NOT NULL, PRIMARY KEY (`ALERT_ID`), FULLTEXT KEY `IX_ALERT_COMMENT_SOURCE_CODE` (`ALERT_COMMENT`, `ALERT_SOURCE`) ); Thanks in Advance Gava

1 0

Cannot Start MariaDB
by gw1500 22 Jul '24

22 Jul '24

I've just installed maria on ubuntu but cannot start mariadb: *× mariadb.service - MariaDB 10.6.18 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2024-07-21 16:12:47 UTC; 54s ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 3483 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Process: 3484 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 3486 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set> Process: 3515 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Main PID: 3515 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" CPU: 114ms Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [Note] InnoDB: Starting shutdown... Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [Note] Plugin 'FEEDBACK' is disabled. Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [ERROR] Failed to initialize plugins. Jul 21 16:12:47 dap002 mariadbd[3515]: 2024-07-21 16:12:47 0 [ERROR] Aborting Jul 21 16:12:47 dap002 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Jul 21 16:12:47 dap002 systemd[1]: mariadb.service: Failed with result 'exit-code'. Jul 21 16:12:47 dap002 systemd[1]: Failed to start MariaDB 10.6.18 database server. *I searched for this error (Unknown storage engine Aria) but the solution is to remove the log from /var/log/mysql. However, that directory is empty. If ubuntu puts that log somewhere else I cannot find it. Can someone point me in the right direction for resolving this? TIA.

3 5

MaxScale BSL licensing
by stephan.vos＠metacom.net 12 Jul '24

12 Jul '24

Hi, I need some clarification with regards to the BSL license for MaxScale: Licensed Work: MariaDB MaxScale (TM) version 22.08 The Licensed Work is (c) 2022 MariaDB Corporation Ab Additional Use Grant: You may use the Licensed Work when your application uses the Licensed Work with a total of less than three server instances in production. The the server instances above refer to the servers on which MaxScale is installed or does it refer to the number of database servers that each MaxScale instance monitors. For example can I have MaxScale installed on 5 application servers which then monitors two or less database servers without a license?

3 4

Upgrade from MariaDB 10.6 to 11.4
by stephan.vos＠metacom.net 05 Jul '24

05 Jul '24

I only see details on the website on how to upgrade from 11.6 to 10.11. https://mariadb.com/kb/en/upgrading-from-mariadb-10-6-to-mariadb-10-11/ Does this mean in order to get to 11.4 safely I first have to upgrade to 10.11 and then to 11.4? Has anyone managed to upgrade directly from 10.6 to 11.4 without issues?

3 4

MyISAM packed tables is uncompressed when index is added.
by Vassilis Virvilis 02 Jul '24

02 Jul '24

Hi, The question: Is uncompressing a myisam table when adding an index the expected behavior? Here is the story: I have a very big table so I thought to compress it. I used myisampack which worked great. The table.MYD shrank in size. myisamchk -ddv shows the table as compressed. I noticed the documentation that urges to run: myisamchk -rq after myisampack and I thought: Maybe I shouldn't create any indices on the uncompressed table since myisamchk will redo the work. But if I try to add an index to the compressed table suddenly it gets expanded to its original size and myisamchk -ddv does report the table a uncompressed. So the only solution is to: 1. add the indices in the uncompressed table 2. compress the table 3. run myisamchk -rq [--sort-index --analyze --parallel-recover --tmpdir=/somewhere/with/a/lot/of/space] 4. mysqladmin flush-tables; But this duplicates the index creations step. So is this the expected behavior? * If yes: why? Expanding the table behind the user's back is surprising... * If no: Should I report it as a bug? Here is how to replicate: #DROP TABLE IF EXISTS txxx; CREATE TABLE txxx (id INT, value TEXT); INSERT INTO txxx SELECT 1, REPEAT('A', 65536); *# Let's go to shell *ls -ltr txxx.* -rw-rw---- 1 mysql mysql 466 Jun 30 19:34 txxx.frm -rw-rw---- 1 mysql mysql 1024 Jun 30 19:40 txxx.MYI -rw-rw---- 1 mysql mysql *65548* Jun 30 19:40 txxx.MYD <-- 64K cool *# cool! let's compress *myisampack -f txxx Compressing txxx.MYD: (1 records) - Calculating statistics - Compressing file 87.42% ls -ltr txxx.* -rw-rw---- 1 mysql mysql 466 Jun 30 19:34 txxx.frm -rw-rw---- 1 mysql mysql *8255* Jun 30 19:40 txxx.MYD <-- 8K cool -rw-rw---- 1 mysql mysql 1024 Jun 30 19:41 txxx.MYI # great it is compressed *# because documentation says so: *myisamchk -qr txxx - check record delete-chain - recovering (with keycache) MyISAM-table 'txxx' Data records: 1 ls -ltr txxx.* -rw-rw---- 1 mysql mysql 466 Jun 30 19:34 txxx.frm -rw-rw---- 1 mysql mysql *8255* Jun 30 19:40 txxx.MYD <-- Still compressed -rw-rw---- 1 mysql mysql 1024 Jun 30 19:43 txxx.MYI myisamchk -ddv txxx MyISAM file: txxx Record format: *Compressed* <-------------------------------------!!!! OK Character set: utf8mb3_general_ci (33) File-version: 1 Creation time: 2024-06-30 19:40:36 Recover time: 2024-06-30 19:43:52 Status: checked Checksum: 2613455662 Data records: 1 Deleted blocks: 0 Datafile parts: 1 Deleted data: 0 Datafile pointer (bytes): 6 Keyfile pointer (bytes): 3 Datafile length: 8248 Keyfile length: 1024 Max datafile length: 281474976710654 Max keyfile length: 17179868159 Recordlength: 15 table description: Key Start Len Index Type Rec/key Root Blocksize ro *# Now Let's add the index* ALTER TABLE txxx ADD INDEX(id); *# Shell again *ls -ltr txxx.* -rw-rw---- 1 mysql mysql 958 Jun 30 19:47 txxx.frm -rw-rw---- 1 mysql mysql *65548* Jun 30 19:47 txxx.MYD <--- *Oups - now it is uncompressed* -rw-rw---- 1 mysql mysql 2048 Jun 30 19:47 txxx.MYI myisamchk -ddv txxx MyISAM file: txxx Record format: *Packed* <----------------------------- *Why*? Character set: utf8mb3_general_ci (33) File-version: 1 Creation time: 2024-06-30 19:47:30 Status: changed Data records: 1 Deleted blocks: 0 Datafile parts: 1 Deleted data: 0 Datafile pointer (bytes): 6 Keyfile pointer (bytes): 6 Datafile length: 65548 Keyfile length: 2048 Max datafile length: 281474976710654 Max keyfile length: 288230376151710719 Recordlength: 16 table description: Key Start Len Index Type Rec/key Root Blocksize 1 2 4 multip. long NULL 0 1024 1024

2 2

Can Mariabackup import from a Percona Xtrabackup backup?
by Bryan K. Walton 18 Jun '24

18 Jun '24

Hi, We have a Maria DB 5.5 replica set running on Centos 7. With this OS version about to become end of life, we are planning an upgrade of our replica set to RHEL 9 and Maria DB 10.5. My general plan is to add a new replica secondary to the mix, running Maria DB 10.5 and then promote that server to be primary and replace the other replica members with a new secondary that is also running Maria DB 10.5. My question is, since Mariabackup didn't exist in Maria DB 5.5, is it possible to backup our existing Maria databases with Percona Xtrabackup and then have Mariabackup (from Maria DB 10.5) import that backup on the new server? Thanks, Bryan

2 2

No repo access since two days
by mail＠alexander-palm.de 09 Jun '24

09 Jun '24

Hello there! Sorry, I have no idea where to post this, I hope it's the right place. Since two days I get 403 forbidden errors by apt update at all URLs from mariadb.com I try to get out the reason but I can't. What I have done: - check the trusted.d keys and reinstall it - check if the VHost provider is the problem. So I install a clean new VM at Strato with Ubuntu 22.04 and 24.04 and get the same error on both by using the 'mariadb_repo_setup' script. - install a clean VM at Hetzner whit ubuntu 24.04 and get the same problem by using the 'mariadb_repo_setup' script. I have no Idee what's happend. If I use the URL via curl there is no error. But I can see that the Request to https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu/dists/jammy/In… was redirectet to some cloudflare services with some tokens and timestamps and so on perhaps apt cannot handle that? 3 days before there was no issue with this configuration. Here is a output-example: bash mariadb_repo_setup # [info] Checking for script prerequisites. # [info] MariaDB Server version 11.4 is valid # [info] Repository file successfully written to /etc/apt/sources.list.d/mariadb.list # [info] Adding trusted package signing keys... # [info] Running apt-get update... E: The repository 'http://downloads.mariadb.com/Tools/ubuntu jammy InRelease' is not signed. E: Failed to fetch http://downloads.mariadb.com/Tools/ubuntu/dists/jammy/InRelease 403 Forbidden [IP: 2606:4700::6812:8718 80] E: Failed to fetch https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu/dists/jammy/In… 403 Forbidden [IP: 2606:4700::6811:bf0e 443] E: The repository 'https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu jammy InRelease' is not signed. E: Failed to fetch https://dlm.mariadb.com/repo/maxscale/latest/apt/dists/jammy/InRelease 403 Forbidden [IP: 2606:4700::6811:bf0e 443] E: The repository 'https://dlm.mariadb.com/repo/maxscale/latest/apt jammy InRelease' is not signed. # [error] Failed to add trusted package signing keys Anyone an idea? Thanks, Alex

1 1

Deleted database still present on replica
by Dave Hall 06 Jun '24

06 Jun '24

Hello, If this is not the right place for this question, please feel free to redirect... I am running MariaDB version 10.5.23 in a master/replica configuration with 4 replicas. I recently experienced a failure that required me to restore the DBs on all of my DB systems from backup, including all of my replicas. Somehow in the course of this process I have some databases on my some of my replicas that have been deleted on the master. What is the best way to remove these without confusing or breaking the replication process? Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 1

Aborted connection 0 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Too many connections)
by Rhys.Campbell＠swisscom.com 22 May '24

22 May '24

Hello All, We have a vendor app that attempts a large number of connections and creating the following error in the MariaDB logs (10.11) Aborted connection 0 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Too many connections) Could this error be cause by the vendor app reusing connections that have been idled out on the server side? Rhys

2 1

Deadlock Errors
by Scott Canaan 10 May '24

10 May '24

We have a 3-node Galera cluster running MariaDB 10.5.23. A couple months ago the cluster had an issue and one of my coworkers handled it. We have several cron jobs that run against the databases to gather statistics and other information. One of those jobs runs every 15 minutes. Since the last issue, one SQL in that script has been throwing a deadlock error on two of the three nodes in the cluster: ERROR 1213 (40001) at line 14: Deadlock found when trying to get lock; try restarting transaction I've been monitoring and I don't see the job running more than once at the same time on the same server. The SQL that it is failing on is: insert into rit_mdb_track_logins select report_date, user, count(*) logins from rit_mdb_track_login_detail group by report_date, user; I've run this SQL manually and it works fine. I'm not sure where to go from here. Scott Canaan '88 Sr Database Administrator Information & Technology Services Finance & Administration Rochester Institute of Technology o: (585) 475-7886 | f: (585) 475-7520 srcdco(a)rit.edu<mailto:srcdco@rit.edu> | c: (585) 339-8659 CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.

3 5

TCMalloc with Maria and THPs
by Simon Avery 08 May '24

08 May '24

Hello I'm looking to test tcmalloc for use on our ~80 Maria 10.11.[6-7] servers, running either Rocky 8/9 or Debian 12. A few years ago we moved to using jemalloc which helped resolve or reduce many of the memory leaks on these servers from using the distro's default malloc. We still have a couple of machines where Maria eventually uses all the memory until oomkiller steps in - although we've largely mitigated that by adopting weekly restarts for them. Thanks to Sergei Golubchik for his most useful post here on the 5th on the subject of memory leaks, which has got us looking at tcmalloc and also raises the question of Transparent Huge Pages. Sergei cites several reliable sources recommending turning them off for MariaDb and similar databases. Now - my question; tcmalloc's documentation on tuning at https://google.github.io/tcmalloc/tuning.html says "TCMalloc heavily relies on Transparent Huge Pages (THP)." And explains it's built and tested with THPs enabled and seems to strongly recommend leaving them on. That contradicts the above articles, leaving me confused about which path is best practice. It seems that THP's should be on as advised by tcmalloc, but also off when running MariaDb. The true answer possibly depends on which has the highest priority in terms of database-specific performance and the ability to manage the memory tightly. What are others' views, please? I'm searching in particular for best practice and real world experiences with tcmalloc. Also - if it's unlikely to improve upon jemalloc. Simon Avery Linux Sysadmin: ATASS Sports Oxygen House | Grenadier Road, Exeter Business Park | EX1 3LH t: 01392 440 400 e: simon.avery(a)atass-sports.co.uk<mailto:simon.avery@atass-sports.co.uk> www.atass-sports.co.uk<http://www.atass-sports.co.uk/> Follow us on X: @atassSports<https://twitter.com/atassSports> NOTICE This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy

2 3

Detect INSERT vs REPLACE in BEFORE INSERT trigger
by Alex Hermann 06 May '24

06 May '24

Hi, Is there a (built-in) way to detect from within a BEFORE INSERT trigger whether it was triggered by an INSERT or REPLACE statement? I could surround every REPLACE statement with setting and clearing a variable. Problem is that this could easily be forgotten as there are multiple applications accessing the table. I'd rather not wrap access in a stored procedure or worse. What will not work is to do a SELECT (tailored to every UNIQUE key) to determine if a record will be replaced. I do not need to know if a record _will_ be replaced, just that the intention is that it _can_ be replaced. Background: the trigger does a validation that is not enforcable via a UNIQUE key. This precludes an INSERT ... ON DUPLICATE KEY UPDATE ... construction. When the validation finds a conflicting row, the query must fail when the _intent_ is to add a new record (INSERT), but succeed when the _intent_ is to replace (REPLACE) that row. -- Regards, Alex Hermann

3 2

Excessive memory usage 10.11.6
by Clint Todish 05 May '24

05 May '24

5 6

Re: Detect INSERT vs REPLACE in BEFORE INSERT trigger
by Jaco Kroon 03 May '24

03 May '24

Hi Alex, >> May I assume that it's also not quite as trivial as doing something >> like this: >> >> CONSTRAINT `valid_phone` CHECK (`phoneno` regexp '^0[1-8][0-9]{8}$') > Correct. It does its own conflict detection as UNIQUE keys can't > represent it. I wasn't thinking that the CONSTRAINT needs to be UNIQUE, the above is a CHECK ... which could potentially use a stored function to perform the check ... timing could then possibly again be an issue depending on whether the function will still see the old data or not (https://mariadb.com/kb/en/constraint/#check-constraints has some info, but testing will be required). "One can use most deterministic functions in a constraint, including UDFs <https://mariadb.com/kb/en/user-defined-functions/>." Kind regards, Jaco

2 3

SOUNDEX function
by lucyfrost＠tutanota.com 01 May '24

01 May '24

I'm developing a project which uses soundex matching (amongside other options more sophisticated than that). This is custom software with a mariad back end. MariaDB soundex built-in produces codes of apparently arbitary length; the usual is 4 characters. I've come to the conclusion that the best way forward is to mimic Maria's soundex in the code. I cannt find a desciption of the algorith Maria uses though: the only source code I can find is in mf_soundex.c, and that is explicitly limited wo 4 characters. But I have installed triggers which generate codes such as A4152636125262 Where is the soundex function found? Anyone know?

2 1

testing req/sec
by Marc 26 Apr '24

26 Apr '24

I would like to test how many requests/sec mariadb can process to authenticate users. So I need to be able to test how many cycles I can do of connecting to mariadb, executing the password sql statement and closing the connection. Anyone know what tool I can use for this?

2 3

mysqlcheck/mariadbcheck: consistency check before mysqldump
by Felix Natter 21 Apr '24

21 Apr '24

Dear mariadb experts, I would like to do this to verify my dbs (to detect hardware errors so that I can replay a backup timely): mysqlcheck -u root -pX --check --all-databases --extended Is it definitely read-only? Can I rely on the return code (0=success)? Or do I not need this because "mysqldump" does consistency checks? Many Thanks and Best Regards! Felix -- Felix Natter

2 2

Transaction Log Flushing got worse again in 10.5.23 -> 10.5.24
by Gordan Bobic 16 Apr '24

16 Apr '24

I've mentioned this here a few times before, but it looks like the latest 10.5.x update to 10.5.24 actually made things worse than in 10.5.23. I have attached two screenshots of transaction log checkpoint age over a 5 minute oltp_write_only sysbench test with 10.5.23 and 10.5.24. 10.5.23 starts off with the flushing all or nothing behaviour but it dampens out after the first minute or so. 10.5.24 exhibits it permanently. I ran multiple separate tests and the behaviour is very consistent for each version. 10.5.23 almost (not quite but almost) seems to have had things fixed to a state where things were in 10.5.8. It's pretty bad that whatever causes this undesirable flushing behaviour seems to have been merged as of 10.5.9 (10.5.8 seems to be the newest version that doesn't exhibit it). It's much more concerning that nobody seems to care that the last good major version (10.4) is going EOL soon with apparently no newer long-term tested version that is not broken. I also tested the latest 10.6.17 and that exhibits the same broken behaviour. Is a fix for this behaviour expected any time soon? On high throughput production systems that can have prolonged bursts of large writes that can hit at any time - if they hit at the top of the checkpoint age that the database made no effort to flush, there is no space left in the transaction log to absorb that impact and it leads to stalls. If combined with disk I/O exhaustion, these stalls can be so bad that for a period of tens of seconds or even minutes even the database telemetry gathering starts to fails. I also attached a screenshot with a 10 minute period where 10.5.8 and 10.5.9 were sysbenched back-to-back for 5 minutes each, with an update/restart in the middle. How extensively is the commit that introduced this behaviour built upon in subsequent changes? How much of a rabbit hole am I heading down if I try to cherry-unpick it? The config I tested with is as follows: ``` [mysqld] innodb_buffer_pool_dump_at_shutdown = 0 innodb_buffer_pool_load_at_startup = 0 innodb_buffer_pool_size = 1G innodb_fast_shutdown = 0 # in case a upgrade introduces redo log format change innodb_io_capacity = 2000 innodb_io_capacity_max = 10000 innodb_log_file_size = 256M innodb_log_write_ahead_size=16K innodb_monitor_enable = all innodb_use_native_aio = 0 # native aio is slow on ZFS innodb_use_atomic_writes = 0 # native aio is slow on ZFS ```

3 5

Windows gssapi plug-in with multiple SIDs/Groups
by darrel.fenstad＠gmail.com 15 Apr '24

15 Apr '24

I am using MariaDB 10.117 and gssapi plug-in to allow SID:BA as follows: "ALTER USER `myuser`@`localhost` IDENTIFIED VIA gssapi USING 'SID:BA';" This works fine. But i want to add an additional GROUP besides SID:BA. I have tried: "ALTER USER `myuser`@`localhost` IDENTIFIED VIA gssapi USING 'SID:BA' OR gssapi USING 'GROUP:My Group';" However, when I look at mysql - View - user it shows the authentication_string as only GROUP:My Group. I also tried: "ALTER USER `myuser`@`localhost` IDENTIFIED VIA gssapi USING 'SID:BA', 'GROUP:My Group'; But that showed authentication_string in mysql - View - user as only SID:BA. Is it possible to specify multiple SIDs and GROUPs and, if so, what is the syntax to do so? Regards, Darrel

2 1

Backup MariaDB Databases for Suprema BioStar 2 Door Access System
by Turritopsis Dohrnii Teo En Ming 15 Apr '24

15 Apr '24

Subject: Backup MariaDB Databases for Suprema BioStar 2 Door Access System Good day from Singapore, On 7 March 2024 Thursday, when I was installing new self-signed SSL certificate for the door access system for a law firm in Singapore, I notice that Suprema BioStar 2 also uses the open source MariaDB database server. If I did not remember wrongly, there are 3 databases. However, the entire platform is a Windows environment, not Linux. How can I backup all the databases in the MariaDB database server? Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com GIMP also stands for Government-Induced Medical Problems.

2 2

Why MariaDB 11.4.1 master-slave replication not sync old data
by i18n.site＠gmail.com 07 Apr '24

07 Apr '24

I have a question about an issue I'm facing with MariaDB 11.4.1 (MariaDB 11 should have GTID enabled by default). I am trying to set up a highly available MariaDB (1 master with 2 slaves) using orchestrator. After shutting down the master database, orchestrator automatically switches one of the slave databases (u3) to become the new master (all slaves have log_slave_updates enabled). At this point, I manually create a brand new, empty slave database u2 (with no data) to synchronize with this new master. The Slave_IO_Running and Slave_SQL_Running status on u2 are both Yes. I attempt to create a new database on the master, and it appears on u2 as well. However, the problem is that the old databases present on u3 are not showing up on u2. ( see this image https://p.3ti.site/1712458958.webp ) I have searched online for solutions and it seems like I would need to manually back up the old databases, import them, and then modify the binlog files and synchronization positions. This feels cumbersome and is not convenient for automated recovery. I am wondering if there might be a misconfiguration on my part that is causing this issue.

2 1

Why is configuring init-file causing the error COLLATION 'latin1_swedish_ci' is not valid for CHARACTER SET 'binary'
by i18n.site 07 Apr '24

07 Apr '24

Why is configuring init-file causing the error COLLATION 'latin1_swedish_ci' is not valid for CHARACTER SET 'binary' I use default character-set-server=binary ❯ rg binary conf.d/mariadb.cnf 7:character-set-server=binary 8:collation-server=binary ❯ /usr/local/mysql/bin/mariadbd --init-file=/etc/mysql/init.sql --defaults-file=/etc/mysql/mariadb.cnf 2024-04-07 12:07:40 0 [ERROR] COLLATION 'latin1_swedish_ci' is not valid for CHARACTER SET 'binary' 2024-04-07 12:07:40 0 [ERROR] Aborting ❯ cat /etc/mysql/init.sql STOP SLAVE;CHANGE MASTER TO master_use_gtid=slave_pos, MASTER_USER='sync',MASTER_HOST='xx',MASTER_PORT=2002,MASTER_PASSWORD='xx',MASTER_CONNECT_RETRY=1; START SLAVE; /etc/mysql

1 0

LOCK TABLES FOR WRITE with mysqldump imports
by stephan.vos＠metacom.net 05 Apr '24

05 Apr '24

I noticed that my data archiving process has been adding LOCK TABLES (table) FOR WRITE to the mysqldump file. I am now worried that if I ever need to import this data into the 3 node Galera cluster it will cause deadlocking as described in the MariaDB known issues article. Does MariaDB with Galera still lock up when this statement is executed or would it just ignore the LOCK TABLES command?

1 0

Help - Creating a loop to go through every row in a table, no errors, not working
by ram3n 01 Apr '24

01 Apr '24

Hi all, I've ran into a little roadblock while creating a WHILE loop within a procedure that's intended to go through every row within a table, *world.creature_template*. Query runs fine in my database, no warnings or errors, but it's not actually changing anything at all. Affected rows are always at 0. Link to the code is below, thanks in advance. https://srcb.in/YVuGJQU4o8 Some sample records: entrydifficulty_entry_1difficulty_entry_2difficulty_entry_3KillCredit1 KillCredit2modelid1modelid2modelid3modelid4namesubnameIconNamegossip_menu_id minlevelmaxlevelexpfactionnpcflagspeed_walkspeed_runscalerankdmgschool BaseAttackTimeRangeAttackTimeBaseVarianceRangeVarianceunit_classunit_flags unit_flags2dynamicflagsfamilytypetype_flagslootidpickpocketlootskinloot PetSpellDataIdVehicleIdmingoldmaxgoldAINameMovementTypeHoverHeight HealthModifierManaModifierArmorModifierDamageModifierExperienceModifier RacialLeadermovementIdRegenHealthmechanic_immune_mask spell_school_immune_maskflags_extraScriptNameVerifiedBuild 29 0 0 0 25499 0 25275 0 0 0 Kanrethad Master of Death 0 90 90 0 35 0 1 1.14286 1 0 0 2000 2000 1 1 1 0 2048 0 0 7 0 0 0 0 0 0 0 0 0 1 1250 1 1 1 1 0 0 1 0 0 0 12340 30 0 0 0 0 0 382 0 0 0 Forest Spider 0 5 6 0 22 0 1 0.85714 1 0 0 2000 2000 1 1 1 0 2048 0 3 1 1 30 0 0 5880 0 0 0 SmartAI 1 1 1 1 1 1 1 0 100 1 0 0 0 12340 31 0 0 0 0 0 145 0 0 0 Furbolg 0 1 2 0 35 0 1.2 1.14286 1 0 0 2000 2000 1 1 1 0 2048 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 1 0 0 0 12340 36 0 0 0 0 0 367 0 0 0 Harvest Golem 0 11 12 0 14 0 1 1.14286 1 0 0 2000 2000 1 1 1 0 2048 0 0 9 32768 36 0 0 0 0 13 21 1 1 1 1 1 1 1 0 0 1 16384 0 0 12340 38 0 0 0 0 0 5035 5036 0 0 Defias Thug 0 3 4 0 7 0 1 0.85714 1 0 0 2000 2000 1 1 1 0 2048 0 0 7 0 38 38 0 0 0 2 7 SmartAI 1 1 1 1 1 1 1 0 100 1 0 0 0 12340 40 0 0 0 0 0 373 0 0 0 Kobold Miner 0 6 7 0 26 0 1 0.85714 1 0 0 2000 2000 1 1 1 0 2048 0 0 7 0 40 40 0 0 0 5 12 SmartAI 1 1 1 1 1 1 1 0 100 1 0 0 0 12340 *generated 2024-03-31 22:08:23 by HeidiSQL 12.1.0.6537 <https://www.heidisql.com/>*

1 0