Bug #76341 | Replication with GTID (no binlog) fails - 'Binary log is not open' | ||
---|---|---|---|
Submitted: | 16 Mar 2015 17:10 | Modified: | 22 Aug 2018 17:21 |
Reporter: | eva zangerle | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.7.6 | OS: | Linux (3.10.0-123.9.3.el7.x86_64) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | binglog, replication |
[16 Mar 2015 17:10]
eva zangerle
[22 Aug 2018 17:21]
MySQL Verification Team
Hi, this is not a bug. You must have binlog enabled on master in order for replication to work! https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-howto.html It is not mandatory to have binary logging enabled in order to use GTIDs when using the mysql.gtid_executed Table. *Masters must always have binary logging enabled in order to be able to replicate.* However, slave servers can use GTIDs but without binary logging. If you need to disable binary logging on a slave server, you can do this by specifying the --skip-log-bin and --skip-log-slave-updates options for the slave. kind regards Bogdan