diff options
| author | unknown <knielsen@knielsen-hq.org> | 2013-10-25 12:56:12 +0200 |
|---|---|---|
| committer | unknown <knielsen@knielsen-hq.org> | 2013-10-25 12:56:12 +0200 |
| commit | 80d0dd7babb5ade8345cdd7065e8f9ef6b65e3da (patch) | |
| tree | 7ccbfebc289bc5aa426baaa88c971feb1bb01c35 /sql/rpl_gtid.cc | |
| parent | 7a22b6a6550ef6f798a0f5ff21d645ae43b3cbb2 (diff) | |
| download | mariadb-git-80d0dd7babb5ade8345cdd7065e8f9ef6b65e3da.tar.gz | |
MDEV-4506: Parallel replication.
Do not update relay-log.info and master.info on disk after every event
when using GTID mode:
- relay-log.info and master.info are not crash-safe, and are not used
when slave restarts in GTID mode (slave connects with GTID position
instead and immediately rewrites the file with the new, correct
information found).
- When using GTID and parallel replication, the position in
relay-log.info is misleading at best and simply wrong at worst.
- When using parallel replication, the fact that every single
transaction needs to do a write() syscall to the same file is
likely to become a serious bottleneck.
The files are still written at normal slave stop.
In non-GTID mode, the files are written as normal (this is needed to
be able to restart after slave crash, even if such restart is then not
crash-safe, no change).
Diffstat (limited to 'sql/rpl_gtid.cc')
0 files changed, 0 insertions, 0 deletions