Setting super_read_only=ON on GTID Slave Leads to High CPU Usage

(Doc ID 2294945.1)

Last updated on AUGUST 09, 2017

Applies to:

MySQL Server - Version 5.7 to 5.7 [Release 5.7]
Information in this document applies to any platform.

Symptoms

Slave may display high CPU usage.  SHOW ENGINE INNODB STATUS may show a transaction similar to this :

 

Changes

After enabling super_read_only=ON, the symptoms are showing.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms