Description:
At present not all scenarios of Group membership changes are logged.
When member join or member leaves, customers cannot identify same by looking
at logs. View changes are not logged. Present logging does not assist DBAs with
corrective measures during network partitions or inform DBAs when member
re-connects.
Also at some places we are logging internal debug messages which cannot be decoded
by DBAs.
Important member related configuration is also not logged.

Resolution:
Logging has been analyzed for:
1. View changes
2. Member join
3. Member leave(graceful and crash)
4. Member unreachable
5. Member re-connect
6. Removal of debug messages
7. Member configuration has been extended with Member_id, member_uuid,
   single_primary_mode, and group_replication_auto_increment_increment
8. Improvements in single-primary mode status reporting and member
   leaving/joining logging
New messages have been added and change to existing messages where required has
been done.