This now appears to have been fixed upstream, in November. The flagged commits for this fix are:
""" Both commit ids need to be applied, the second commit id was to fix a test case issue. Pushed into repo mysql branch mysql-5.7 5.7.29 (hash:df622a4e0fd5b919f26ff217047ced988a90e1b4 committer:nisha.gopalakrish...@oracle.com) (merge vers:5.7.29) Pushed into repo mysql branch mysql-5.7 5.7.29 (hash:dc4c221afca22196967252f324431626dafbec06 committer:nisha.gopalakrish...@oracle.com) (merge vers:5.7.29) """ Next action is to retrieve the patches, review them for acceptability per Ubuntu SRU policies, prepare packaging for the fix, and fill in the SRU. If anyone wishes to lend a hand on one or more of these tasks it may help speed this issue towards a fix. For reference, the SRU process is outlined at https://wiki.ubuntu.com/StableReleaseUpdates ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831773 Title: High CPU usage, MySQL process got stuck on "SHOW SESSION VARIABLES LIKE 'FOREIGN_KEY_CHECKS' " To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1831773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
