Here we go with another update of ODBC, our reliable and high-performance tools for connecting to popular databases and cloud services from ODBC-compatible tools. This release features enhanced performance, essential new options, expanded capabilities, and much more.

The post Meet Our Newly Updated ODBC Solutions appeared first on Devart Blog.

Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 8.0, consisting of MySQL-wsrep 8.0.41-26.22 (release notes, download), with Galera replication library 4.22 (release notes, download) implementing wsrep API version 26. It also includes Galera Cluster for MySQL 8.4, consisting of MySQL-wsrep 8.4.4-26.22 (release notes, …

Large tables can pose challenges for many operations when working with a database. Occasionally, we may need to modify the table definition. Since RDS replication does not use asynchronous for its replication, the typical switchover procedure is not feasible. However, the Blue/Green feature of RDS utilizes asynchronous replication, which allows us to update the table […]

This blog was originally published in April 2023, and we thought it was time for an update. The objective remains the same: since nearly all cloud providers offer a MySQL-based cloud service, who provides the best value?   Comparing MySQL cloud services   To answer that question, we compared the cost of the following services: […]

So, as you’ve noticed, I’ve been playing around with MySQL Router v8.4.3 and read-write splitting, and now I’ve come across some issues that my environment has generated and I’ve opened some bugs against the fiend:

Bug 116950 – Router Read-Write splitting config causes PHP RSET_HEADER error

Bug 116951 – mysqlrouter Error parsing stats_updates_frequency errors

Bug 116952 – Router w/ RW split causes ERROR: 4501 if sql script contains comments lines (“– “)

(Yup, I prepared each bug description, repeatable tasks and suggested fix …

I’m just trying out the v8.4 Read-Write configuration for MySQL Router, that comes default in the community edition and, as they say, TL;DR “it’s default upon bootstrap”.

What does this mean and how can I go about it?

The overview is simple:

• Either install or upgrade your existing MySQL Router to v8.4 at least.
• Bootstrap the Router.
• Use the port 3310 or change it to fit your needs.

Let’s get to it:

Stop your running router:

systemctl stop mysqlrouter

Copy the old config, just in case:

cp /etc/mysqlrouter/mysqlrouter.conf /etc/mysqlrouter/mysqlrouter_v80.conf

I normally keep my mysql linux repository disabled so no “yum update” takes over version control and gives me a nasty surprise afterwards. As so, I uncomment the “mysql” entry:

vi /etc/yum.conf …

Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 8.0, consisting of MySQL-wsrep 8.0.40-26.21 (release notes, download), with Galera replication library 4.21 (release notes, download) implementing wsrep API version 26. It also includes Galera Cluster for MySQL 8.4, consisting of MySQL-wsrep 8.4.3-26.21 (release notes, …

MySQL 8.4 and newer have extended the Global Transaction ID (GTID) functionality with a new “tag” option.

Refresher on GTID

A GTID is a unique ID that is assigned to a transaction. This is used if gtid_mode is set to ON. The benefit of this is that a transaction can be uniquely identified in a MySQL replication setup with multiple levels. Among others this makes it easier to refactor a replication tree as a MySQL replica knows which transactions it has seen and can use this to find the right position to start replicating from a new source.

The format of GTIDs is documented here.

Before GTID was used replication worked based on a file and offset (e.g. file=binlog.000001,offset=4), which is unique to every server.

A GTID without tag looks like …

The latest update to MySQL Enterprise edition, version 9.1, introduces significant enhancements focused on replication monitoring. This update includes improvements to Group Replication Flow Control and the replication applier, providing users with better visibility and control over their replication performance, leading to potential long-term cost savings by ensuring efficient usage of their machine resources.

Different ways to get the status:

mysqlsh --login-path=icadmin -h$MYROUTER1 -- cluster status

mysqlsh --login-path=icadmin -h${HOSTNAME} --redirect-primary -- cluster status

mysqlsh icadmin:'P4ssw0rD'@db01:3306 -- cluster status --extended=0

mysqlsh icadmin@$MYROUTER1:3306 -- cluster status --extended=1

watch -n 5 “mysqlsh --login-path=icadmin -h$MYROUTER1 -- cluster status”

Set the Primary Instance (switching):

mysqlsh --login-path=icadmin -h${HOSTNAME} --redirect-primary -- cluster set_primary_instance "db01"

Obtaining MySQL InnoDB Cluster basics:

select cluster_id, cluster_name, description, cluster_type, primary_mode, clusterset_id from mysql_innodb_cluster_metadata.clusters;

Members of our cluster:

select * from performance_schema.replication_group_members order by MEMBER_ROLE;

Local & Remote Trans Q’s:

 …