Bug #89060 ASSERT ON SET GLOBAL GTID_MODE ON AN OFFLINE (READ_ONLY) MEMBER
Submitted: 26 Dec 2017 19:28 Modified: 21 Feb 2018 16:50
Reporter: Narendra Chauhan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Group Replication Severity:S3 (Non-critical)
Version:8.0.11 OS:Any
Assigned to: CPU Architecture:Any

[26 Dec 2017 19:28] Narendra Chauhan
Description:
Scenario: Verify setting of RPL variables in GR environment with different GR modes.
Expected output: In READ_ONLY mode, either the affecting variable settings should be blocked or there must be no ASSERTION failure.
Actual output: Assertion failure.

mysqld.2.err:-
===============
....
2017-12-26T19:19:24.744367Z 11 [System] [MY-010035] Changed GTID_MODE from ON to ON_PERMISSIVE.
mysqld: /Narendra/mysql_work/git_repo/mysql-8.0/sql/sql_error.cc:407: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `! is_set()' failed.
19:19:24 UTC - mysqld got signal 6 ;
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=131072
max_used_connections=7
max_threads=151
thread_count=6
connection_count=5
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68194 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fe4603db840
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 = 7fe4bdac8d38 thread_stack 0x46000
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(my_print_stacktrace+0x55) [0x3ec3773]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(handle_fatal_signal+0x424) [0x30493b9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7fe4c6816390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x7fe4c55b8428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7fe4c55ba02a]
/lib/x86_64-linux-gnu/libc.so.6(+0x2dbd7) [0x7fe4c55b0bd7]
/lib/x86_64-linux-gnu/libc.so.6(+0x2dc82) [0x7fe4c55b0c82]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(Diagnostics_area::set_ok_status(unsigned long long, unsigned long long, char const*)+0x75) [0x2c56341]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(my_ok(THD*, unsigned long long, unsigned long long, char const*)+0x4e) [0x2c4df49]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(mysql_execute_command(THD*, bool)+0x27aa) [0x2cb4792]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(mysql_parse(THD*, Parser_state*)+0x65e) [0x2cb9ff4]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x129c) [0x2caf9cd]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld(do_command(THD*)+0x484) [0x2cae391]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld() [0x30390e1]
/Narendra/mysql_work/git_repo/mysql-8.0/install/bin/mysqld() [0x450ebdc]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7fe4c680c6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fe4c568a3dd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe4600e8a00): SET GLOBAL gtid_mode=2
Connection ID (thread ID): 11
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
safe_process[24043]: Child process: 24044, killed by signal: 6

How to repeat:
Details:-
=========
Version checked: 8.0.5

Steps to repro:-
=================
Run command: ./mtr group_replication.gr_bug1.test

Where,
$ cat gr_bug1.test
--source ../inc/have_group_replication_plugin.inc
--let $rpl_skip_group_replication_start= 1
--let $rpl_group_replication_single_primary_mode=1
--source ../inc/group_replication.inc

# Start group replication on all the servers
--source ../inc/start_and_bootstrap_group_replication.inc
--let $member1_uuid= query_get_value(SELECT @@SERVER_UUID, @@SERVER_UUID, 1)

--let $rpl_connection_name= server2
--source include/rpl_connection.inc
--source include/start_group_replication.inc

# Making sure this is the primary server
--let $group_replication_expected_uuid= $member1_uuid
--source ../inc/gr_wait_primary_member_uuid.inc

--let $skip_reset_read_mode=1
--source include/stop_group_replication.inc

SELECT @@super_read_only, @@read_only;

SET GLOBAL gtid_mode=2;

--source ../inc/group_replication_end.inc
[21 Feb 2018 16:50] David Moss
Posted by developer:
 
Thank you for your feedback, this has been fixed in upcoming versions and the following was added to the 5.7.22 / 8.0.11 changelog:
Changing the Group Replication required settings incorrectly on online secondary members could result in an unexpected halt.
[31 May 2018 14:54] David Moss
Reclosing.