run optimize table got [Note] WSREP: MDL BF-BF conflict and [ERROR] Aborting

one of our Galera DB cluster got one DB node status wsrep_ready changed to OFF when application running "optimize table". We need to restart the DB node in order to resume the cluster.

Below is from debug log. Kindly help to advise how to avoid the node down.

2022-12-26 1:00:00 1 [Note] WSREP: wsrep_commit_empty(1)
2022-12-26 1:00:00 1 [Note] WSREP: assigned new next trx id: 9201958
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_before_prepare: 1
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_after_prepare: 1
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_before_commit: 1, 22083004
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_ordered_commit: 1
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_after_commit: 1, 1, 22083004, 0
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_after_apply 1
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_commit_empty(7)
2022-12-26 1:00:00 7 [Note] WSREP: assigned new next trx id: 9201959
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_before_prepare: 1
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_after_prepare: 1
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_before_commit: 1, 22083005
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_ordered_commit: 1
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_after_commit: 1, 1, 22083005, 0
2022-12-26 1:00:00 7 [Note] WSREP: wsrep_after_apply 7
2022-12-26 1:00:00 6 [Note] WSREP: Wsrep_high_priority_service::apply_toi: 22083006
2022-12-26 1:00:00 6 [Note] WSREP: assigned new next query and trx id: 9201960
2022-12-26 1:00:00 6 [Note] WSREP: Apply TOI Begin: ANALYZE TABLE oss_sup_doc
2022-12-26 1:00:00 6 [Note] WSREP: Apply TO END: 22083006: ANALYZE TABLE oss_sup_doc
2022-12-26 1:00:00 6 [Note] WSREP: Set WSREPXid for InnoDB: 92b3ac91-e636-11ec-ae4a-2348379544ba:22083006
2022-12-26 1:00:00 8 [Note] WSREP: Wsrep_high_priority_service::apply_toi: 22083007
2022-12-26 1:00:00 8 [Note] WSREP: assigned new next query and trx id: 9201961
2022-12-26 1:00:00 8 [Note] WSREP: Apply TOI Begin: OPTIMIZE TABLE oss_sup_doc
2022-12-26 1:00:00 8 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_commit_empty(1)
2022-12-26 1:00:00 1 [Note] WSREP: assigned new next trx id: 9201962
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_before_prepare: 1
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_after_prepare: 1
2022-12-26 1:00:00 1 [Note] WSREP: wsrep_before_commit: 1, 22083008
2022-12-26 1:00:00 8 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files
2022-12-26 1:00:00 8 [Note] WSREP: MDL conflict
schema: swdcisdb
request: (8 seqno 22083007 wsrep (toi, exec, committed) cmd 0 45 OPTIMIZE TABLE oss_sup_doc)
granted: (1 seqno 22083008 wsrep (high priority, exec, committing) cmd 0 161 (null))
2022-12-26 1:00:00 8 [Note] WSREP: MDL ticket: type: MDL_SHARED_READ space: TABLE db: swdcisdb name: oss_sup_doc (Waiting for table metadata lock)
2022-12-26 1:00:00 8 [Note] WSREP: MDL BF-BF conflict
schema: swdcisdb
request: (8 seqno 22083007 wsrep (toi, exec, committed) cmd 0 45 OPTIMIZE TABLE oss_sup_doc)
granted: (1 seqno 22083008 wsrep (high priority, exec, committing) cmd 0 161 (null))
2022-12-26 1:00:00 8 [Note] WSREP: MDL ticket: type: MDL_SHARED_READ space: TABLE db: swdcisdb name: oss_sup_doc (Waiting for table metadata lock)
2022-12-26 1:00:00 8 [ERROR] Aborting