Athens - Replication in MariaDB - notes
You are viewing an old version of this article. View
the current version here.
Note: This page is obsolete. The information is old, outdated, or otherwise currently incorrect. We are keeping the page for historical reasons only. Do not rely on the information in this article.
Overview of Replication in MariaDB: Replication
In MariaDB 5.3:
- Group Commit for the binary log.
- Mark Callaghan from Facebook did some benchmarks:
- The Facebook patch and the implementation in MariaDB 5.3 are two different solutions to the same problem. The latest Facebook patch is close to the performance in MariaDB, but MariaDB is still faster.
- Benchmarking thread scheduling in group commit, part 2
- Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT
- Is actually consistent now ...
- non-blocking slave privisioning
- Annotation of row-based replication events with the original SQL statement
- A separate, but very similar, implementation is in 5.6
- Row-based replication for tables with no primary key
- PBXT consistent commit ordering
- Binlog Event Checksums (backport from MySQL 5.6
To be in MariaDB 5.5
@@do_not_replicate
Additional:
- Fixing
rpl_transaction_enabledin case we crash and rollback during XA
Misc:
- This preview also includes a small change to make mysqlbinlog omit redundatn use statements around BEGIN, SACEPOINT, COMMIT, and ROLLBACK events when reading MySQL 5.0 binlogs.
- The preview included a feature
--innodb-release-locks-early. However we decided to omit this feature from future MariaDB releases because of a fundamental design bug, Bug #798213
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
