This is caused by binary log Binlog_snapshot_file and Binlog_snapshot_position status variables, getting which tries to take LOCK_log with LOCK_status already locked. LOCK_log is taken by the committing thread which has a lot of work to binlog the file load, and LOCK_status is what all connection threads try to take in THD::release_resources
This is caused by binary log Binlog_ snapshot_ file and Binlog_ snapshot_ position status variables, getting which tries to take LOCK_log with LOCK_status already locked. LOCK_log is taken by the committing thread which has a lot of work to binlog the file load, and LOCK_status is what all connection threads try to take in THD::release_ resources