MySQL Unconference #008 was held

 
Yuta Kikai (Service Reliability Group (SRG) of the Media Headquarters)@fat47)is.
#SRG(Service Reliability Group) is a group that mainly provides cross-sectional support for the infrastructure of our media services, improving existing services, launching new ones, and contributing to OSS.
This article introduces MySQL Unconference #008, which was held recently.
 

What is MySQL Unconference?


MySQL Unconference to be held in February 2024@tom__boIt was started by Mr. and is run as a casual event where people can talk about MySQL casually, regardless of company boundaries.
Thoughts on the eventThis is tom__bo's blogPlease see.
 
From this time onwards, I will be co-hosting@fat47and@mconfjpWith the addition of Mr./Ms. Ito, we have established a system that will allow us to continue holding events.

MySQL Unconference #008 Overview


At this year's MySQL Unconference #008, the three organizers each gave a session, and the event mainly consisted of casual conversations that developed from those sessions.

Presentation 1: "Aurora Blue/Green Deployment Feature Supports Non-Disruptive Upgrades of Large-Scale Aurora MySQL Clusters"

The first announcement is me@fat47was carried out.
Ameba Blog explains how they upgraded a large-scale Aurora MySQL cluster using the Aurora Blue/Green Deployment feature, and provides an overview of the feature.
Click here for the document
 
When explaining the B/G function, we used diagrams to explain the switching process.
I also mentioned the problems I encountered,
We will introduce the fact that it is difficult to check the replication status between Blue/Green at a glance from the console, and how to address the slowness of SELECT COUNT as examples.

Presentation 2: "Reading the MySQL Online DDL (INPLACE) Code with Help from Claude"

The second one is Morita-san (@mconfjp) and his presentation was about using Claude to read the source code of the OnlineDDL part of MySQL.
Click here for the document
 
In the past, he had researched the mechanism of online DDL and summarized it in a blog, but he challenged himself to deepen his understanding by reading the actual MySQL source code.
MySQL's source code is huge and it would be difficult to read it from scratch, so by using the generative AI Claude to read through it, they were able to get a rough grasp of its structure.

Presentation 3:Aiming for safe DDL execution ~(Part 1) Understanding the MDL to be obtained~

Finally,@tom__boThis presentation will deepen your understanding of Metadata Locking (MDL) by Mr.
Click here for the document
 
MDL is a lock acquired to manage concurrent access to database objects and ensure consistency when changing table structure, etc.
This was being investigated because a better understanding of MDL would allow for safer DDL execution.
 
MDL can be checked via the performance_schema.metadata_locks table, but this only shows locks that are being acquired or waited for.
 
Therefore@tom__boHe investigated the issue by modifying the MySQL source code and adding detailed log output using the print debugging method.

Next event schedule and call for speakers


MySQL Unconferences will continue to be held every three months.
Next time #009Around July 2025The event is scheduled to be held, so if you are interested, please feel free to join us!
X's community function "#MySQLUnconference", so if you enter there we will be able to let you know as soon as the date of the event is decided.
 
Someone who will talk to youCurrently accepting applicationsis.
This does not only apply to MySQL alone, but also covers any issues or problems related to MySQL-compatible products on each public cloud, MariaDB, and Percona for MySQL.
Five-minute short talks and longer presentations are also welcome, so please feel free to contact the organizer (@tom__bo , @mconfjp , @fat47) I would be happy if you could contact me.
It's okay to not have to prepare presentation materials, but just decide on a theme and have participants exchange opinions with each other.