On MyNA- MySQL Japanese User Group. Q&A with Tsubasa Tanaka
Q1. You are the vice organizer of the MySQL Japanese User Group, known as MyNA. Who is involved in MyNA?
MyNA besides me has 3 more board members:
– Organizer, Masahiro Tomita.
– Vice-organizer, Yasushi Tsutsui.
– Vice-organizer, Kei Sakai.
They are the first members to have started using MySQL in Japan.
My colleagues on the MyNA board had the chance to present the User Group during a dedicated episode of the MySQL Community podcast, Inside MySQL: Sakila Speaks
Q2: You are part of the MyNA User Group. Can you tell us more about your role and what MyNA is about?
MyNA is a loose community. There are no strict roles and schedules. I’m one of the most active members on MyNA and was elected to the board due to my involvement in such activities.
Q3. Why did you decide to use MySQL?
There were two reasons why I started using MySQL (on Windows, not Linux) in the late 2000s.
One was replication. PostgreSQL didn’t have a native replication feature, and pgpool-II didn’t work on Windows.
The other was pronunciation. “My-Ess-Que-Ell” is easier to say than “Post-gres-Que-Ell” for me.
Q4. So, you started using MySQL because of replication. What for?
I used it for circular replication, which should not be used and can break in many cases. And this is what happened to me, too. As I wasn’t a database operator, this forced me to learn some DBA tasks, such as backups, restoration, and fixing replication.
Q5. Since you started with MySQL, replication must have undergone significant changes. Hasn’t it?
Indeed, for example, I don’t see any reason why people shouldn’t use GTIDs nowadays.
However, for me, who has to deploy many asynchronous replication environments, the use of MySQL ReplicaSet, combined with MySQL Shell and Clone, is highly valued.
I regularly use these features in production.
Q6. What are you using MySQL for?
I have worked for a WEB service company as a DBA. They are using MySQL to store their various service data.
For example, mailing lists, chats, photos’ metadata, game savedata, settlement histories, employees’ information, etc.
Q7. You have been awarded MySQL 5.7 Community contributor. What are your most important contributions?
My most important contribution to MySQL 5.7 was not a code contribution.
That was a reporting user’s voice about “default_password_lifetime” introduced by 5.7.
Bug #77277 default_password_lifetime should be set to 0 as the implicit default value
Until 5.7.11, the default value of default_password_lifetime was 360.
This meant “the account that was created and has not changed its password gets to be shut down after 360 days”.
This behavior was a huge incompatibility and too dangerous. I had informed a caveat about this to local MySQL User Groups and bugs.mysql.com (that was Bug#77277)
And finally, the MySQL Developers decided to change their default settings in order to protects all MySQL users.
……………………………………………………………….
Tsubasa Tanaka Vice-organizer of MySQL Japanese User Group, named MyNA.
Known as yoku0825 in the Japanese MySQL Community. Oracle ACE Pro (MySQL) since March, 2014. Maintainer of innotop. Co-author of “Introduction to MySQL thoroughly(MySQL徹底入門)” and “Introduction to MySQL Operations Management Practice(MySQL運用・管理 [実践] 入門)”. He was awarded MySQL 5.7 Community contributor.
Home Page: https://yoku0825.blogspot.jp
Sponsored by MySQL/Oracle.