Shinguz's blog

FromDual is pleased to announce the release of the new version 1.2.2 of the popular FromDual Ops Center focmm, a Graphical User Interface (GUI) for MariaDB, MySQL and compatible databases.

• Ops Center 1.2.2 Release Notes: FromDual Ops Center 1.2.2 for MariaDB, MySQL and compatible databases has been released (2024-04-25)
• Ops Center 1.2.1 Release Notes: FromDual Ops Center 1.2.1 for MariaDB, MySQL and compatible databases has been released (2023-02-07)
• Ops Center 1.2.0 Release Notes: FromDual Ops Center 1.2.0 for MariaDB, MySQL and compatible databases has been released (2023-01-17)
• Ops Center 1.1.0 Release Notes: FromDual Ops Center for MariaDB, MySQL and compatible databases 1.1.0 has been released (2021-05-07)
• Ops Center 1.0.0 Release Notes: FromDual Ops Center for MySQL and compatible databases 1.0.0 has been released (2020-05-07)
• Ops Center 0.9.3 Release Notes: FromDual Ops Center for MariaDB and MySQL 0.9.3 has been released (2020-02-18)
• Ops Center 0.9.2 Release Notes: FromDual Ops Center for MariaDB and MySQL 0.9.2 has been released (2019-08-13)
• Ops Center 0.9.1 Release Notes: FromDual Ops Center for MariaDB and MySQL 0.9.1 has been released (2019-05-07)
• Ops Center 0.9.0 Release Notes: FromDual Ops Center for MariaDB and MySQL 0.9 has been released (2019-04-16)
• Ops Center 0.3.0 Release Notes: FromDual Ops Center for MySQL and MariaDB 0.3 has been released (2016-01-13)
• Ops Center 0.2.0 Release Notes: FromDual Ops Center for MySQL and MariaDB 0.2.0 has been released (2014-05-29)
• Ops Center 0.1.0 Release Notes: FromDual Ops Center for MySQL and MariaDB 0.1.0 has been released (2014-01-02)
• Ops Center 0.0.1 Release Notes: FromDual Ops Center for MySQL and MariaDB 0.0.1 has been released (2014-01-01)

Table of contents

• Review
• One month later
• Size of the tables
• Process list
• Global variables
• Metadata Lock and InnoDB Transaction Lock
• Global status

Review

After we introduced dbstat for MariaDB (and MySQL) a good 5 weeks ago, we naturally also rolled it out on our systems to test the behaviour in daily use (eat your own dog food).

Due to an application error, our replication stopped for 5 days (over Easter). After the problem was solved, the replication was supposed to catch up, which turned out to be very slow. All the usual tricks (innodb_flush_log_at_trx_commit, sync_binlog, etc.) had already been exhausted. So we tried our hand at parallel replication of the MariaDB server.

Recently I had to test a new MariaDB feature that was developed at our request (MDEV-33782). To test this feature I had to build the MariaDB server myself from source, which I have not done for a long time. So a new challenge, especially with CMake…

Table of contents

• Overview
• Preparations
• Activate MaxScale configuration synchronisation
• Change MaxScale parameters
• Add new slave and make MaxScale known
• Remove old slave and make MaxScale known
• How is the configuration synchronised?
• What happens in the event of a conflict?
• Tests
• Deactivating MaxScale configuration synchronisation again
• Literature/sources

Overview

A feature that I recently discovered while browsing is the MaxScale configuration synchronisation functionality.

Table of contents

• Overview
• Preparation of the shards (MariaDB database instances)
  • Create test data
  • Creating roles and users
  • MaxScale Monitor User
  • MaxScale Admin User
  • Create application role and accounts
  • Proxy protocol
• MaxScale SchemaRouter configuration
• Starting and stopping the MaxScale Load Balancer
• Application tests
  • Simple application tests
  • New command show shards
  • More general test
  • Less simple tests
  • More complex application tests
  • Cross-shard tests
• Operation of a MaxScale sharding system
  • Do-on-all-shards
  • Invalidating the database map cache
  • How to change SchemaRouter variables dynamically?
  • Adding and removing a tenant
  • Moving a tenant
  • Adding or removing a shard
  • Customising the configuration files
  • Maintenance work on the shard
• Observation / monitoring of a MariaDB MaxScale sharding system
• Literature / Sources

Overview

This feature should more or less work with MariaDB MaxScale 6.x.y, 22.08.x, 23.02.x, 23.08.x and 24.02.x. We have tested it with the latest MaxScale version 23.08.05, as we encountered problems with an older version (MXS-5026).

Table of contents

• Functionality of dbstat
• How does dbstat work
• How to install dbstat
• Query dbstat
  • table_size
  • processlist
  • trx_and_lck
  • metadata_lock
  • global_variables
  • global_status
• Testing
• Sources

An idea that I have been thinking about for a long time and have now, thanks to a customer, finally tackled is dbstat for MariaDB/MySQL. The idea is based on sar/sysstat by Sebastien Godard:

FromDual has the pleasure to announce the release of the new version 2.1.0 of its popular MariaDB, Galera Cluster and MySQL multi-instance environment MyEnv.

• MyEnv 2.1.0 Release Notes: MariaDB/MySQL Environment MyEnv 2.1.0 has been released (2024-02-28)
• MyEnv 2.0.3 Release Notes: MariaDB/MySQL Environment MyEnv 2.0.3 has been released (2021-07-02)
• MyEnv 2.0.2 Release Notes: MariaDB/MySQL Environment MyEnv 2.0.2 has been released (2019-01-17)
• MyEnv 2.0.1 Release Notes: MariaDB/MySQL Environment MyEnv 2.0.1 has been released (2018-10-03)
• MyEnv 2.0.0 Release Notes: MySQL Environment MyEnv 2.0.0 has been released (2018-03-15)
• MyEnv 1.3.1 Release Notes: MySQL Environment MyEnv 1.3.1 has been released (2016-08-03)
• MyEnv 1.3.0 Release Notes: MySQL Environment MyEnv 1.3.0 has been released (2016-01-31)
• MyEnv 1.2.2 Release Notes: MySQL Environment MyEnv 1.2.2 has been released (2015-10-12)
• MyEnv 1.2.1 Release Notes: MySQL Environment MyEnv 1.2.1 has been released (2015-07-27)
• MyEnv 1.2.0 Release Notes: MySQL Environment MyEnv 1.2.0 has been released (2015-04-18)
• MyEnv 1.1.4 Release Notes: MySQL Environment MyEnv 1.1.4 has been released (2015-02-11)
• MyEnv 1.1.2 Release Notes: MySQL Environment MyEnv 1.1.2 has been released (2014-10-23)
• MyEnv 1.1.1 Release Notes: MySQL Environment MyEnv 1.1.1 has been released (2014-09-08)
• MyEnv 1.1.0 Release Notes: MySQL Environment MyEnv 1.1.0 has been released (2014-08-23)
• MyEnv 1.0.5 Release Notes: MySQL Environment MyEnv 1.0.5 has been released (2014-06-13)
• MyEnv 1.0.4 Release Notes: MySQL Environment MyEnv 1.0.4 has been released (2014-04-29)
• MyEnv 1.0.3 Release Notes: MySQL Environment MyEnv 1.0.3 has been released (2014-04-25)
• MyEnv 1.0.2 Release Notes: MySQL Environment MyEnv 1.0.2 has been released (2013-12-11)
• MyEnv 1.0.1 Release Notes: MySQL Environment MyEnv 1.0.1 has been released (2013-11-05)
• MyEnv 1.0 Release Notes: MySQL Environment MyEnv 1.0 has been released (2013-10-04)

The design of a data warehouse differs from relational design. Data warehouses are often designed according to the concept of the star schema.

FromDual has the pleasure to announce the release of the new version 2.1.0 of its popular Database Performance Monitor for MariaDB and Galera Cluster fpmmm.

Translated by deepl.com

Introduction

Two points in advance:

1. A deadlock is a state in which two different transactions are no longer able to continue working because each transaction holds a lock that the other transaction would need. Because both transactions are now waiting for the other transaction to release their locks, neither transaction will release their respective locks. And that would last forever. To avoid this, the MariaDB instance intervenes and kills the transaction that has done less work. The application then receives a deadlock error message of this type:

Scenario: MariaDB Community Server is release every 3 months. The exact date is not known but it is typically about 2 to 3 weeks after the MySQL/Oracle CPU.

FromDual has the pleasure to announce the release of the new version 1.2.1 of its popular FromDual Ops Center focmm, a Graphical User Interface (GUI) for MariaDB, MySQL and compatible databases.

FromDual has the pleasure to announce the release of the new version 1.2.0 of its popular FromDual Ops Center focmm, a Graphical User Interface (GUI) for MariaDB, MySQL and compatible databases.

Table of Contents

• SystemD Notizen
• InnoDB NUMA interleave with MariaDB
• Checking Galera Cluster SST timeout with SystemD
• Kill MariaDB Galera node under SystemD
• MariaDB Memory locking (--memlock) with SystemD
• Who is restarting my mariadbd?
• Location of SystemD unit files

SystemD Notizen

SystemD paged per default nach less. Das ist ungewohnt und doof, weil es gegen allgemeines Linux-Verhalten verstösst. Abhilfe schafft:

A while ago I read a paper about Optimizer Benchmarks: How Good Are Query Optimizers, Really? by Viktor Leis from Fakultät für Informatik of the Technische Universität München.

Before you consider migrating your data from MySQL to another database you have to know which objects have to be migrated.