Description:
This is Feature Request.
MySQL uses datadir/GSC_DEBUG_TRACE for debugging Group Replication's behavior.
But there is no way reopen GSC_DEBUG_TRACE.
So once GSC_DEBUG_TRACE is fat, can't rotate and/or remove GSC_DEBUG_TRACE file without restarting Group Rplication now.
I hope to add reopening funtion for GCS_DEBUG_TRACE, like a "FLUSH GCS LOGS".
How to repeat:
$ lsof GCS_DEBUG_TRACE
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mysqld 20530 mysql 50w REG 202,1 116831 42112470 GCS_DEBUG_TRACE
### Once GCS_DEBUG_TRACE is too big, filesystem is exhausted, "SET GLOBAL group_replication_communication_debug_options = GCS_DEBUG_NONE" and remove the file!
$ rm GCS_DEBUG_TRACE
$ ls GCS_DEBUG_TRACE
ls: cannot access GCS_DEBUG_TRACE: No such file or directory
### But mysqld still has filehandle, not release volume of filesystem..
$ lsof -p $(pidof mysqld) | grep GCS
mysqld 20530 mysql 50w REG 202,1 119988 42112470 /var/lib/mysql/GCS_DEBUG_TRACE (deleted)
I confirmed "STOP GROUP_REPLICATION" releases GCS_DEBUG_TRACE file and "START GROUP_REPLICATION" re-creates the file, but I need these "reopen" without restarting Group Replication.
Suggested fix:
Add function like a "FLUSH GSC LOGS"
