Bug #81297 Error thrown in super_read_only mode when stopping slave sql_thread

• Submitted: 3 May 2016 17:16
• Modified: 4 May 2016 11:41
• Reporter: Ceri Williams
• Status: Duplicate
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 5.7
• OS: Any
• CPU Architecture: Any

[3 May 2016 17:16] Ceri Williams

Description:
An error is emitted when stopping the slave sql_thread in super_read_only mode using relay_log_repository = TABLE:

ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement

How to repeat:
Set:

- relay_log_repository = TABLE
- super_read_only = 1

Issue: 

- stop slave sql_thread;

Suggested fix:
Allow this table to be written to in super_read_only mode

[3 May 2016 17:18] Ceri Williams

Correcting a missed typo - relay_log_info_repository

[4 May 2016 5:50] MySQL Verification Team

Hello Ceri Williams,

Thank you for the report.
Could you please confirm us the exact MySQL version you are using? If you are using MySQL version < 5.7.12 then you may have to upgrade because related Bug #78963 is fixed in 5.7.12 and as per change log:

5.7.12 changelog:

When a server was running with relay_log_info_repository=TABLE and the --super-read-only option enabled, a statement which caused an update to the slave info tables, such as STOP SLAVE or CHANGE MASTER TO, resulted in a 'STOP SLAVE' failed: 1290: The MySQL server is running error, preventing the statement being executed. The fix ensures that replication operations are permitted regardless of the setting of read_only and super_read_only.

Thanks,
Umesh