Avoid GC conflicts in replication setups
Avoid GC conflicts in replication setups

Try to avoid a conflict when running garbage collection simultaneously on two
MySQL servers at a very busy site.

The conflict could lead to synchronization failures when trying to delete
session records on both servers:

    Could not execute Delete_rows event on table sessions; Can't find record in
    'sessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND

pematon/mysql-session-handler