|   登录   |   注册   |   设为首页   |   加入收藏   

用户登录

close

用户名:

密码:

新用户注册

close

用户名:

密码:

密码确认:

电子邮箱:

关注内容:

个人主页:

帮助

close

龙宇网成立于2008年3月,网站进入整体运作于2010年10月1日。

在这里,我们把它做成了一个真正意义上的网站,完全以个人的信息为内容,以网友的需要为主导,全力搜罗各种信息,建立完善的网站功能,使网友在这里可以第一时间找到所需要的信息。

现在,经过三年的努力,网站的资料已经相当丰富,而网站得到了大家的喜爱和认可。

但,我们还是会继续努力下去,让网间的这份快乐继续持续下去,让这份闲暇时的日子,与快乐一并同行。

寻觅快乐,网住快乐,关注网络,是龙宇网的宣言与承诺。

Server version in the binary log

分类: 存储 发布时间: 2019-03-27 15:42:28 浏览次数: 149
内容提要: Replication topologies, whether master-slave or group replication setups, may be composed of servers using different MySQL versions.

Replication topologies, whether master-slave or group replication setups, may be composed of servers using different MySQL versions.

In MySQL 8.0.14, each transaction’s immediate and original server versions are now visible in the binary log as session variables. These two new variables, fully managed by the replication infrastructure, are used to support cross-version replication by transmitting the MySQL server release numbers associated with each transaction through the replication topology:

  • original_server_version stores the MySQL Server release number of the server where a transaction was originally committed (for example, 80014 for a MySQL 8.0.14 server instance).
  • immediate_server_version stores the MySQL Server release number of the server that is the immediate master in the replication topology (i.e., the last server where the transaction was applied).

Below is an excerpt on a binary log showing the Gtid log event of a transaction in which both original and immediate masters’ MySQL Server versions were 8.0.14.

在每个event上都添加了这几个参数吗?

1

2

3

4

5

6

7

8

#190117 13:02:24 server id 1 end_log_pos 1250 CRC32 0xd7c0725c GTID last_committed=4 sequence_number=5 rbr_only=no original_committed_timestamp=1547730144863243 immediate_commit_timestamp=1547730144863243 transaction_length=203

# original_commit_timestamp=1547730144863243 (2019-01-17 13:02:24.863243 WET)

# immediate_commit_timestamp=1547730144863243 (2019-01-17 13:02:24.863243 WET)

/*!80001 SET @@session.original_commit_timestamp=1547730144863243*//*!*/;

/*!80014 SET @@session.original_server_version=80014*//*!*/;

/*!80014 SET @@session.immediate_server_version=80014*//*!*/;

SET @@SESSION.GTID_NEXT= 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:5'/*!*/;

# at 1250

 

The new variables improve the auditing and debugging of replication issues in topologies with servers of different versions. They also improve the support of replication from servers running older MySQL releases.

If there is a server in the replication topology that does not support this feature (its version number is older than 8.0.14), then all transactions replicated from that server will have original and immediate server versions set to ‘000000’.

We look forward to hearing your feedback on this new feature!

 

原文链接:

https://mysqlhighavailability.com/server-version-in-the-binary-log/

15
20

分类: 存储   |   评论: 0   |   引用: 0   |   浏览次数: 149