Bug #102548 semi-sync replication with ogg
Submitted: 10 Feb 2021 2:59 Modified: 3 Apr 2021 5:09
Reporter: HULONG CUI Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.22 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: semi-sync

[10 Feb 2021 2:59] HULONG CUI
Description:
Description:
1)I have  one master  two slave with semi-sync replication .
  and  setting  mysql binlog to oracle use ogg.

2) crash error log:
when mysql command show_slave_hosts; this is hang  after crash
####
mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=1048576
max_used_connections=159
max_threads=1024
thread_count=64
connection_count=63
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3167616 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f828020fde0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f83e257cea8 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0xf4b6d5]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x4a4)[0x7d0d74]
/lib64/libpthread.so.0(+0xf370)[0x7f8971afa370]
/usr/local/mysql/bin/mysqld(pfs_start_mutex_wait_v1+0x17)[0x1255157]
/usr/local/mysql/bin/mysqld(_Z14get_slave_uuidP3THDP6String+0x6f)[0xefdeaf]
/usr/local/mysql/bin/mysqld(_Z16show_slave_hostsP3THD+0xa88)[0xf00528]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THDb+0x2a4d)[0xd1806d]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x40d)[0xd1aaad]
/usr/local/mysql/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x119a)[0xd1bcca]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1cb74]
/usr/local/mysql/bin/mysqld(handle_connection+0x29c)[0xdedaec]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x174)[0x1256a94]
/lib64/libpthread.so.0(+0x7dc5)[0x7f8971af2dc5]
/lib64/libc.so.6(clone+0x6d)[0x7f89705b073d]
########

Other error:
2021-02-10T06:29:40.622149+08:00 728 [Note] Aborted connection 728 to db: 'unconnected' user: 'ogg' host: '*.*.*.*' (Failed on my_net_write())
2021-02-10T06:29:40.745417+08:00 729 [Note] Stop asynchronous binlog_dump to slave (server_id: 958840896)
2021-02-10T06:29:40.814955+08:00 730 [Note] Stop asynchronous binlog_dump to slave (server_id: 958840896)
2021-02-10T06:29:40.815035+08:00 730 [Note] Aborted connection 730 to db: 'unconnected' user: 'ogg' host: '*.*.*.*' (Failed on my_net_write())
2021-02-10T06:29:40.890298+08:00 731 [Note] Stop asynchronous binlog_dump to slave (server_id: 958840896)

I guess semi-synchronous checking for ogg replication  and  doesn't check  2 slave replication,

How to repeat:
mysql 1master 2 replicat  + ogg setting
replication account same 

Suggested fix:
setting weight for each replicat set order number,semi-sync replication check verify the large weights first。
[10 Feb 2021 13:53] MySQL Verification Team
Hi,

Thanks for the report. Can you reproduce this with 5.7.33 ?

kind regards
Bogdan
[3 Mar 2021 4:49] HULONG CUI
Because this is  readl user  environment cannot be upgraded。

Is there another way check or to identify the problem
[3 Mar 2021 5:09] MySQL Verification Team
Hi,

> environment cannot be upgraded

The fix cannot be applied without an upgrade so if the environment can't be upgraded you for sure can't fix it. 

I cannot reproduce this issue with the modern version of MySQL Server and there are a number of changes in the semi-sync replication since your version, so unless you can reproduce this with the latest version there's nothing I can do.
[4 Apr 2021 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".