Bug #84798 Group Replication can use some verbosity in the error log
Submitted: 2 Feb 2017 14:32 Modified: 22 Sep 2017 15:41
Reporter: Kenny Gryp Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Group Replication Severity:S3 (Non-critical)
Version:5.7.17 OS:Any
Assigned to: CPU Architecture:Any

[2 Feb 2017 14:32] Kenny Gryp
Description:
with log_error_verbosity=3 and log_warnings=2 (the only settings I can think of right now that might increase verbosity) I do not get much group replication messages:

How to repeat:
Play around, create some network partitions, tail -f error log and see nothing

Suggested fix:
The error log should contain:
- A new view_id does not get logged
- When a member got disconnected it is not logged
- When a member lost connection with another member it is not logged
- When a member joins the cluster again (https://bugs.mysql.com/bug.php?id=84784)
- probably more....
[3 Feb 2017 12:53] Umesh Shastry
Hello Kenny,

Thank you for the report and feedback.

Thanks,
Umesh
[22 Sep 2017 15:41] 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.20 / 8.0.4 changelog:
The logging of Group Replication has been improved. Now logging includes information when a member joins or leaves, when the view changes, and so on.