WSREP donor crashes after changing status from donor to joined

It does not always happen. When it happens, we can observe logs like below:

[Note] WSREP: Server status change donor -> joined

[Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.

[ERROR] WSREP: Certification exception: Attempt to match against an empty key (1,0): 22 (Invalid argument) at / bitnami/blacksmith-sandbox/libgalera-26.4.7/galera/src/key_set.cpp:throw_match_empty_key():174

[Note] WSREP: ReplicatorSMM::abort()

[Note] WSREP: Closing send monitor...

[Note] WSREP: Closed send monitor.

[Note] WSREP: gcomm: terminating thread

[Note] WSREP: gcomm: joining thread

[Note] WSREP: gcomm: closing backend

...

[Note] WSREP: New SELF-LEAVE.

[Note] WSREP: Flow-control interval: [0, 0]

[Note] WSREP: Received SELF-LEAVE. Closing connection.

[Note] WSREP: Shifting OPEN -> CLOSED (TO: 1585314378)

[Note] WSREP: RECV thread exiting 0: Success

...

[ Note] WSREP: recv_thread() joined.

[ Note] WSREP: Closing replication queue.

[ Note] WSREP: Closing slave action queue.

[Note] WSREP: /opt/bitnami/mairadb/sbin/mysqld: Terminated.

...