Bug #91793 Use the new shutdown service when gr_exit_state_action=ABORT_SERVER
Submitted: 25 Jul 2018 16:25 Modified: 9 Jan 2019 14:23
Reporter: Nuno Carvalho Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Group Replication Severity:S4 (Feature request)
Version:8.0.12 OS:Any
Assigned to: CPU Architecture:Any

[25 Jul 2018 16:25] Nuno Carvalho
On WL#11568: "Group Replication: option to shutdown server when dropping out of the group" we did introduce the option group_replication_exit_state_action, which when set to ABORT_SERVER, in the case of a Group Replication error the server would be aborted by calling abort().

WL#12003: "Component interface to deliver signals to the host application" introduced a service through which a plugin can instruct the server to shutdown instead of calling abort().

This bug will replace the abort by the new shutdown service call.

Also this bug will remove the lines:
 --source include/have_debug.inc
 --source include/not_valgrind.inc
that were added to several tests to avoid MTR consider this expected behaviour a unexpected server crash.
The bug assigned must find which tests need to be updated, one of them is gr_exit_state_action_on_applier_error.test

How to repeat:
Please see abort_plugin_process() on plugin/group_replication/src/plugin_utils.cc

Suggested fix:
I will upload a draft patch.
[9 Jan 2019 14:23] David Moss
Posted by developer:
Thank you for your feedback, this has been fixed in upcoming versions and the following was added to the 8.0.14 / 8.0.14 changelog:
When group_replication_exit_state_action is set to ABORT_SERVER, the Group Replication plugin now uses the new component service added by WL#12003 to shutdown MySQL.