Bug #108825 Timestamps needed in the GCS_DEBUG_TRACE file
Submitted: 19 Oct 2022 10:26 Modified: 19 Oct 2022 10:50
Reporter: Przemyslaw Malkowski Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Group Replication Severity:S4 (Feature request)
Version:8.0.31 OS:Any
Assigned to: CPU Architecture:Any
Tags: group replicaiton

[19 Oct 2022 10:26] Przemyslaw Malkowski 
Description:
After enabling one of the debug modes via group_replication_communication_debug_options, the result log file GCS_DEBUG_TRACE does not contain timestamps. It makes it pretty hard to investigate when you have to pinpoint some events from the past and for example compare this log to the regular error log.

How to repeat:
Enable any of the available debug modes:

set global group_replication_communication_debug_options=GCS_DEBUG_BASIC;

The log is without timestamps:
$ tail -f data/GCS_DEBUG_TRACE
[MYSQL_GCS_DEBUG] [GCS] Initializing peers
[MYSQL_GCS_DEBUG] [GCS] Configured total number of peers: 3
...

Suggested fix:
Add timestamps to the debug log.
[19 Oct 2022 10:50] MySQL Verification Team 
Hello Przemyslaw,

Thank you for the reasonable feature request!

Thanks,
Umesh
[21 Nov 2022 10:17] MySQL Verification Team 
Bug #109144 marked as duplicate of this one