Shlomi Noach
code.openark.org · Personal blog · on HN since 2009
Shlomi Noach, MySQL engineer and author of gh-ost and orchestrator, writes on MySQL replication, schema changes and foreign keys.
What HN saysCommenters cite it as an authoritative source on MySQL high availability, orchestrator, foreign key limits and online schema changes.
15HN people shared it
5linked it in comments
11stories submitted
139story points
2 years agolast shared
2009people per year2026
Most-shared posts
- 1SQL pie chart4 people · 19 points · first shared 2009 · 1 comments on HN
- 2The problem with MySQL foreign key constraints in Online Schema Changes (2021)2 people · 46 points · first shared 2023 · 7 comments on HN
- 3Mysql high availability tools followup the missing piece orchestrator2 people · first shared 2017
- 4How not to test that mysqld is alive1 people · 65 points · first shared 2009 · 22 comments on HN
- 5Things that don’t work well with MySQL’s FOREIGN KEY implementation1 people · 3 points · first shared 2023 · discussion on HN
- 6Observations on the hashicorp/raft library, and notes on RDBMS1 people · 2 points · first shared 2017 · discussion on HN
- 7How to convince MySQL to use the right index1 people · 2 points · first shared 2012 · discussion on HN
- 8Making charts in SQL1 people · 1 points · first shared 2015 · discussion on HN
- 9Refactoring MySQL replication topologies visually1 people · 1 points · first shared 2014 · discussion on HN
- 10Mysql vs postgresql gh ost perspective1 people · first shared 2018
- 11Openark kit1 people · first shared 2018
What HN people wrote when they linked it
fipar · 2017-12-07
I think it's relevant that Baron's post mentions a Github incident, and Github has been doing automatic failover of MySQL masters for a while now: https://githubengineering.com/orchestrator-github/
This post is also very relevant to the topic: http://code.openark.org/blog/mysql/mysql-high-availability-tools-follo…
The post you link is still relevant to this discussion, but we can't ignore that 5 years have passed. It would be good to see 2017's Baron revisit the topic :)
sciurus · 2017-07-06
The author of Orchestrator also goes into questions like that at http://code.openark.org/blog/mysql/mysql-high-availability-tools-follo…
Tangentially, in that blog post I was impressed by the list of companies running orchestrator.
> orchestrator is actively maintained by GitHub. It manages automated failovers at GitHub. It manages automated failovers at Booking.com, one of the largest MySQL setups on this planet. It manages automated failovers as part of Vitess. These are some names I’m free to disclose, and browsing the issues shows a few more users running failovers in production. Otherwise, it is used for topology management and visualization in a large number of companies such as Square, Etsy, Sendgrid, Godaddy and more.
grep_it · 2023-12-21
The responder to that issue has also written some blog posts that go into more detail on the subject.
* https://code.openark.org/blog/mysql/things-that-dont-work-well-with-my…
* https://code.openark.org/blog/mysql/the-problem-with-mysql-foreign-key…
shlomi-noach · 2018-05-03
Author of gh-ost here. Here are my thoughts on migrating to a different RDBMS: http://code.openark.org/blog/mysql/mysql-vs-postgresql-gh-ost-perspect…
michaeldejong · 2018-03-24
Indeed. It seems there are many such tools available for MySQL: Openark kit [0] for instance, whose author also brought us gh-ost. Unfortunately most tools focus on just MySQL, and none really have an answer when you want to use (and enforce) foreign key constraints. Although it's hard to say, I suspect the users of these tools have "given up" on foreign key constraints.
[0] http://code.openark.org/forge/openark-kit
[1] https://github.com/github/gh-ost