| Bug #90046 | suspect error code in Pipeline_event::convert_log_event_to_packet | ||
|---|---|---|---|
| Submitted: | 13 Mar 2018 13:24 | Modified: | 12 Apr 2018 5:52 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Group Replication | Severity: | S4 (Feature request) |
| Version: | 5.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[14 Mar 2018 4:36]
MySQL Verification Team
Hello Shane, Thank you for the report and feature request! Thanks, Umesh
[12 Apr 2018 5:52]
Erlend Dahl
Duplicate of Bug#87701 members are exited from GR when 1/3 node tried to rejoin after shutdown under he

Description: Take a look in .\mysql-5.7\rapid\plugin\group_replication\include\pipeline_interfaces.h int convert_log_event_to_packet() { int error= 0; ... if ((error= log_event->write(cache))) { log_message(MY_ERROR_LEVEL, "Unable to convert the event into a packet on the applier!" " Error: %d\n", error); /* purecov: inspected */ return error; /* purecov: inspected */ } AFAIK log_event->write returns a bool. In error logs these days we see things like: [ERROR] Plugin group_replication reported: 'Unable to convert the event into a packet on the applier! Error: -7 So, what is -7 ? How to repeat: Don't treat bool as int.