mysql-5.6

Facebook's branch of the Oracle MySQL database. This includes MyRocks.

Data & Databases

Explore on GitHub Read Hacker News discussions

14Distinct people

17Mentions

0Explicit recommenders

2.6KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Facebook's branch of the Oracle MySQL database. This includes MyRocks.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2015-05-06 02:23:37 UTC to 2021-12-06 09:44:12 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	1
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	7	7
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	4	4
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	4	4

What Hacker News says

17 sources

elktea·Dec 6, 2021

as we are all discussing the pros and cons of various DBs, my favourite MySQL feature has to be the pluggable storage engines. Being able to support both InnoDB and RocksDB backed tables in the same database is wonderful. Just today I made use of the MyRocks storage engine's handy TTL [1] feature instead of a tedious delete & optimise scheduled job [1]https://github.com/facebook/mysql-5.6/wiki/Time-to-Live-%28T...

In Leaving MySQL

krilovsky·Oct 9, 2021

Note: while it is based on MariaDB, it replaces InnoDB (the MariaDB/MySQL storage engine) with MyRocks (which is based on RocksDB), and as a consequence it is missing some features (such as foreign keys[1]) that prevent it from being usable in many applications. [1] https://github.com/facebook/mysql-5.6/wiki/MyRocks-limitatio...

In EdgelessDB: A Database Designed for Confidential Computing

HarrisonFisk·Jul 22, 2021

Direct source is available at: https://github.com/facebook/mysql-5.6 The social graph is indeed stored in MySQL via TAO. A recent white paper about MyRocks is: https://research.fb.com/publications/myrocks-lsm-tree-databa...

In Migrating Facebook to MySQL 8.0

HarrisonFisk·Jul 22, 2021

The code is open source: https://github.com/facebook/mysql-5.6

In Migrating Facebook to MySQL 8.0

yoshinorim·Sep 16, 2020

I am one of the creators of MyRocks at FB. We have a few common MySQL features/operations we don't use at FB. Notably: 1) Schema Changes by DDL (e.g. ALTER TABLE, CREATE INDEX) 2) Recovering primary instances without failover We use our own open source tool OnlineSchemaChange to do schema changes (details: https://github.com/facebook/mysql-5.6/wiki/Schema-Changes), which is heavily optimized for MyRocks use cases like utilizing bulk loading for both primary and secondary keys. ALTER TABLE / CREATE INDEX support in MyRocks is limited and suboptimal -- it does not support Online/Instant DDL (so blocking writes to the same table during ALTER), and enters non bulk loading path and trying to load the entire table in one transaction -- which may hit row lock count limit or out of memory. We have plans to improve regular DDL paths in MyRocks in

Read the rest

MySQL 8.0, including supporting atomic, online and instant schema changes. I am also realizing that a lot of external MySQL users still don't have auto failover and try to recover primary instances if they go down. This means single instance availability and recoverability is much more important for them. We set rocksdb_wal_recovery_mode=1 (kAbsoluteConsistency) by default in MyRocks, which actually degraded recoverability (higher chances to refuse to start even if it can be recovered from binlog). We're changing defaults to 2 (kPointInTimeRecovery) so that it can be more robust without relying on replicas for recovery. It would have been a really bad experience when hitting OOM by 1) then failing to restart because of 2). We have relations with MariaDB and Percona, and will make default behavior better for users.

In Pebble: A RocksDB Inspired Key-Value Store Written in Go

perlgeek·Dec 3, 2017

Since there seems to be a lot of confusion around transactions in MyRocks: https://github.com/facebook/mysql-5.6/wiki/Transaction-Isola... > MyRocks supports two of the four transaction isolation levels: Read committed and Repeatable reads Repeatable Reads in the default isolation level you get with InnoDB as well (though you can also use "serializable", which MyRocks does not support): https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-i... MySQL does not support transactions that span multiple storage engines (to the best of my knowledge), so you should try to avoid tables with different storage engines within the same database. At least if you need transactions.

In MyRocks – A RocksDB storage engine with MySQL

antoncohen·Dec 3, 2017

Not transactional in what way? Their "Limitations" doc doesn't mention that it lacks transactions (https://github.com/facebook/mysql-5.6/wiki/MyRocks-limitatio...). They have a "Transaction Isolation" doc that describes some options and differences (https://github.com/facebook/mysql-5.6/wiki/Transaction-Isola...).

In MyRocks – A RocksDB storage engine with MySQL

nwrk·Dec 3, 2017

More juicy details is here https://github.com/facebook/mysql-5.6/wiki Also Percona backs it: https://www.percona.com/blog/2016/10/24/announcing-myrocks-i...

In MyRocks – A RocksDB storage engine with MySQL

noahdesu·Jul 9, 2017

This was a good introduction, but I expected to see some detail regarding the table mapping strategy and concurrency control / isolation levels. In addition to InnoDB and SQLite cited in the article, there is also a lot of good information on the MyRocks wiki on mapping the relational model onto a RocksDB-based storage engine: https://github.com/facebook/mysql-5.6/wiki/MyRocks-record-fo...

In SQL in CockroachDB: Mapping Table Data to Key-Value Storage (2015)

jivid·Oct 28, 2016

We take logical backups, not physical, and mysqldump is the best option for that. Having logical backups means we can do logical diffs as well (see https://youtu.be/Fe2oLZ4CWD4?t=951), and we've added table checksum support to mysqldump in our branch of MySQL (https://github.com/facebook/mysql-5.6/commit/54acbbf915935a0...)

In Continuous MySQL backup validation: Restoring backups

jivid·Oct 28, 2016

There's a few different ways to verify, a few of them involving stopping replication, like you pointed out. These can also sometimes be quite expensive, so depending on the type of verification required, the verification method can be tuned. We also implemented table checksums inside of mysqldump, allowing us to dump out the restored data and compare checksums as well, if required. https://github.com/facebook/mysql-5.6/commit/54acbbf915935a0...

In Continuous MySQL backup validation: Restoring backups

0xmohit·Aug 3, 2016

MySQL does need improvements. This [0] is an example. [0] https://github.com/facebook/mysql-5.6

In Thoughts on Uber’s List of Postgres Limitations

midom·Jul 26, 2016

As long as you can shard (across multiple instances, or even within same instance, to avoid B-Tree latching), 1B+ rows within MySQL is piece of cake. Also, MySQL* is getting LSM-Tree support lately, which makes high performance data ingestion combined with OLTP workload quite feasible. * https://github.com/facebook/mysql-5.6/tree/webscalesql-5.6.2...

In Why Uber Engineering Switched from Postgres to MySQL

0xmohit·Jul 26, 2016

Facebook maintains it's own fork [0] of MySQL. A couple of interesting talks are also available: MySQL at Facebook, Current and Future [1] and Massively Distributed Backup at Facebook Scale [2]. [0] https://github.com/facebook/mysql-5.6 [1] https://www.youtube.com/watch?v=jqwegP9xwVE [2] https://www.youtube.com/watch?v=UBHcmP2TSvk

In Why Uber Engineering Switched from Postgres to MySQL

Thaxll·May 24, 2016

Their MySQL version is pretty much the vanilla version, from your post it sounds like it's very different but it's not. https://github.com/facebook/mysql-5.6

In Scaling to 100M: MySQL Is a Better NoSQL

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.