Showing entries 1603 to 1612 of 44809
« 10 Newer Entries | 10 Older Entries »
Unlock the Secrets of MySQL corrupted indexes

One of our customers recently had a Corrupted Index that affected the health of his database and caused latency for his customers. To identify and handle a corrupted index in MySQL, here are some common FAQs:

What is a MySQL corrupted index?

A MySQL corrupted index refers to a situation where the index data within a MySQL database becomes inconsistent or damaged, resulting in incorrect or incomplete query results. It can occur due to various reasons, such as hardware failures, software bugs, improper shutdowns, or disk errors.

What are the common symptoms of a MySQL corrupted index?

When a MySQL index is corrupted, you may experience several symptoms, such as slow query performance, incorrect or missing query results, frequent crashes or errors during database operations, or unusually high CPU or disk usage.

What are the common error messages related to MYSQL Index Corruption?

You can receive …

[Read more]
MySQL at FOSSASIA 2023 Report

In 2023, FOSSASIA returned as a physical event after 2 years of being virtual. With this comeback, the MySQL team was again part of the 2023 edition with MySQL keynote, several technical sessions and the MysQL booth.   Despite the fact that only 200 participants turned out to be from the initially announced 1000 expected […]

MySQL at FOSSASIA 2023 Report

FOSSASIA Apr 2023

Query and Transaction size in MySQL

Some times it’s important to know the size of a transaction, especially when you plan to migrate to a HA solution where by default transactions have a limited size to guarantee an optimal behavior of the cluster.

Today we will see the different possibilities to have an idea of the size of transactions.

First we need to split the transaction in two types:

  • those generating data (writes, like insert, delete and update, DML)
  • those only ready data (select, DQL)

To implement High Availability, only the first category is important.

Size of DML

To know the size of a DML transaction, the only possibility we have is to parse the binary log (or query the binlog event).

We need to check the binlog event from the binlog file and then calculate its size. To illustrate this, let’s try to find the transaction identified by a specific GTID: …

[Read more]
Query and Transaction size in MySQL

In this article you will learn how to retrieve the size of a transaction, DML or DQL in MySQL.

MySQL HeatWave on AWS is now available in AWS Asia Pacific (Tokyo) region

MySQL HeatWave on AWS is now available in AWS Asia Pacific (Tokyo) region MySQL HeatWave on AWS is now available in Japan Tokyo region. The new region enables customers with applications deployed in the Tokyo region to: Minimize network latency between the application and database, enhancing the user experience on the application Reduce the high […]

MySQL HeatWave on AWS is now available in AWS Asia Pacific (Tokyo) region

MySQL HeatWave on AWS is now available in AWS Asia Pacific (Tokyo) region

Query and Transaction size in MySQL

Some times it’s important to know the size of a transaction, especially when you plan to migrate to a HA solution where by default transactions have a limited size to guarantee an optimal behavior of the cluster. Today we will see the different possibilities to have an idea of the size of transactions. First we […]

How to get client’s IP address when using MySQL Router ?

When you connect to a server (or cluster) using a TCP proxy level 7, also referred to as an application-level or Layer 7 proxy (highest level of the OSI model), the application doesn’t connect directly to the back-end server(s). The proxy usually understands the protocol used and can eventually take some decisions or even change the request.

The problem when using such proxy (like HA Proxy, ProxySQL and MySQL Router) is that the server doesn’t really know from where the client is connecting. The server sees the IP address of the proxy/router as the source IP of the client.

HA Proxy initially designed the Proxy Protocol, a simple protocol that allows a TCP connection to transport proxy-related information between the client, the proxy server and the destination server. The main purpose of the Proxy Protocol is then to preserve the client’s original IP address (with some others metadata). See …

[Read more]
How to get client’s IP address when using MySQL Router ?

When you connect to a server (or cluster) using a TCP proxy level 7, also referred to as an application-level or Layer 7 proxy (highest level of the OSI model), the application doesn’t connect directly to the back-end server(s). The proxy usually understands the protocol used and can eventually take some decisions or even change […]

Showing entries 1603 to 1612 of 44809
« 10 Newer Entries | 10 Older Entries »