As upstream bug mentions http://dev.mysql.com/doc/refman/5.6/en /replication-features-timezone.html: "By default, master and slave servers assume that they are in the same time zone. If you are replicating between servers in different time zones, the time zone must be set on both master and slave. Otherwise, statements depending on the local time on the master are not replicated properly, such as statements that use the NOW() or FROM_UNIXTIME() functions. Set the time zone in which MySQL server runs by using the --timezone=timezone_name option of the mysqld_safe script or by setting the TZ environment variable. See also Section 17.4.1.15, “Replication and System Functions”. "
Since you use time_zone SYSTEM behavior with RBR is expected (everything is local to slave). However behavior for SBR/MIXED is not expected as, again, mentioned in the upstream bug: > [29 Jan 2014 17:26] Jon Stephens > > The result that the submitter says that he's obtaining in Step 5--the same > column showing the same literal value on both master and slave--is exactly > the opposite of what we'd expect. If this happens consistently, it's a bug. ** Tags added: upstream ** Bug watch added: MySQL Bug System #71016 http://bugs.mysql.com/bug.php?id=71016 ** Also affects: mysql-server via http://bugs.mysql.com/bug.php?id=71016 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to MySQL. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1720080 Title: replicated TIMESTAMP filed wrong value on slave To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1720080/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : [email protected] Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
