We’re excited to announce our new Continuent Tungsten Clustering MySQL Use Case Webinar Series for 2020 with Eero Teerikorpi, Founder & CEO of Continuent.
Tags: MySQL tungsten clustering Webinar use case High Availability data protection geo-scale Geo-Distributed …
[Read more]When I speak about MySQL performance troubleshooting (or frankly any other database), I tend to speak about four primary resources which typically end up being a bottleneck and limiting system performance: CPU, Memory, Disk, and Network.
It would be great if when seeing what resource is a bottleneck, we could also easily see what queries contribute the most to its usage and optimize or eliminate them. Unfortunately, it is not as easy as it may seem.
First, MySQL does not really provide very good instrumentation in those terms, and it is not easy to get information on how much CPU usage, Disk IO, or Memory a given query caused. Second, direct attribution is not even possible in a lot of cases. For example, disk writes from flushing data from the InnoDB buffer pool in the …
[Read more]The Automatic Schema Synchronization mechanism, detailed in a two part series: part 1 and part 2, automatically detects and synchronizes mismatches in metadata between NDB Dictionary and MySQL Server’s Data Dictionary. Information about the mechanism is exposed through different MySQL Server status variables.…
Tweet Share
ProxySQL is proud to announce the release of the latest stable version of ProxySQL 2.0.13 on the 15th of July 2020
ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.
Release Overview Highlights
New Features
Although only bug fixes are supposed to go into ProxySQL 2.0, we had to introduce a few minor new features:
Date and time values are some of the most important datatypes in
an RDBMS. From tracking order dates to payroll hours,
DATE and DATETIME datatypes are used in
all types of applications. At times as a Developer, you may need
only certain portions of a DATE or
DATETIME value. In MySQL, the EXTRACT()
function can provide you with a specific component of a
DATE or DATETIME value depending on
which INTERVAL is given as a parameter. Continue
reading to see example EXTRACT() queries for
understanding…
Photo by Omar Al-Ghossen on Unsplash …
[Read more]There is a new MySQL 8.0 release and it has some interesting replication features. The change log is available at the usual place, MySQL 8.0.21, but let me give you a brief summary.
… Tweet Share
We are pleased to announce the release of MySQL Cluster 8.0.21, the latest GA, along with 7.6.15, 7.5.19, 7.4.29, and 7.3.30. MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: In-Memory storage – Real-time performance (with optional checkpointing to disk) Transparent Auto-Sharding – Read & write scalability Active-Active/Multi-Master geographic replication 99.999% […]
Dear MySQL users,
MySQL Shell 8.0.21 is a maintenance release of MySQL Shell 8.0
Series (a
component of the MySQL Server). The MySQL Shell is provided
under
Oracle’s dual-license.
MySQL Shell 8.0 is highly recommended for use with MySQL Server
8.0 and
5.7. Please upgrade to MySQL Shell 8.0.21.
MySQL Shell is an interactive JavaScript, Python and SQL
console
interface, supporting development and administration for the
MySQL
Server. It provides APIs implemented in JavaScript and Python
that
enable you to work with MySQL InnoDB cluster and use MySQL as a
document
store.
The AdminAPI enables you to work with MySQL InnoDB cluster and
InnoDB
ReplicaSet, providing integrated solutions for high availability
and scalability
using InnoDB based MySQL databases, without requiring advanced
MySQL
expertise. For more …
Dear MySQL users,
MySQL Shell 8.0.20 is a maintenance release of MySQL Shell 8.0
Series (a
component of the MySQL Server). The MySQL Shell is provided
under
Oracle’s dual-license.
MySQL Shell 8.0 is highly recommended for use with MySQL Server
8.0 and
5.7. Please upgrade to MySQL Shell 8.0.20.
MySQL Shell is an interactive JavaScript, Python and SQL
console
interface, supporting development and administration for the
MySQL
Server. It provides APIs implemented in JavaScript and Python
that
enable you to work with MySQL InnoDB cluster and use MySQL as a
document
store.
The AdminAPI enables you to work with MySQL InnoDB cluster and
InnoDB
ReplicaSet, providing integrated solutions for high availability
and scalability
using InnoDB based MySQL databases, without requiring advanced
MySQL
expertise. For more …
In MySQL 8.0.21, we can see who and how mysqld was
stopped and when the process ended.
Let’s have a look at different scenarios in this article.
SHUTDOWN SQL statement
The first test is to initiate the shutdown of MySQL from a SQL client:
mysql> shutdown;
In the error log (log_error_verbosity is set to 2, the default), we can see:
2020-07-14T07:17:28.865274Z 10 [System] [MY-013172] [Server]
Received SHUTDOWN from user root. Shutting down mysqld (Version: 8.0.21).
2020-07-14T07:17:31.258884Z 0 [System] [MY-010910] [Server]
/usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21) MySQL Community Server - GPL.
We can easily identify when the server started the shutdown process and when it finished.
Stopping using systemd
…[Read more]