Bug #109144 GCS_DEBUG_TRACE lacks timestamps

• Submitted: 19 Nov 2022 5:03
• Modified: 21 Nov 2022 13:25
• Reporter: Marcos Albe (OCA)
• Status: Duplicate
• Category: MySQL Server: Group Replication
• Severity: S2 (Serious)
• Version: 8.0.31
• OS: Any
• CPU Architecture: Any

[19 Nov 2022 5:03] Marcos Albe

Description:
The GCS_DEBUG_TRACE log lacks timestamps, making it much less friendly for troubleshooting.

How to repeat:
node1:
SET GLOBAL group_replication_communication_debug_options=GCS_DEBUG_ALL;
STOP GROUP_REPLICATION;
START GROUP_REPLICATION;

node2:
SET GLOBAL group_replication_communication_debug_options=GCS_DEBUG_ALL;
STOP GROUP_REPLICATION;
START GROUP_REPLICATION;

Check the GCS_DEBUG_TRACE in your datadir, you will be able to verify there's a rampant absence of timestamps

Suggested fix:
Add timestamps to logging in the GCS debug macros (I guess)

[21 Nov 2022 5:34] MySQL Verification Team

Hello Marcos,

Thank you for the report and feedback.

Thanks,
Umesh

[21 Nov 2022 10:16] MySQL Verification Team

Hello Marcos,

Please note that this is duplicate of FR - Bug #108825.
For now marking this as a duplicate of Bug #108825.

regards,
Umesh

[21 Nov 2022 13:25] Marcos Albe

Hey Umesh,
Thanks and sorry, I did quick google search for GCS_DEBUG_TRACE in bugs.mysql.com and didn't found anything :-?   All the same: thanks for handling!

[21 Nov 2022 14:26] MySQL Verification Team

Hello Marcos,

Same with me, even I missed it but product lead was kind enough to let me know and all good now :)

Sincerely,
Umesh