On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

How to change the innodb_log_file_size value in MySQL/MariaDB

Follow

Comments

4 comments

  • Avatar
    Robert

    should point 6 not be START instead of STOP?

    1
    Comment actions Permalink
  • Avatar
    Kuzma Ivanov

    Thanks, Robert!

    That was fixed.

    0
    Comment actions Permalink
  • Avatar
    Omkar More

    Kuzma Ivanov Do we need to configure anything else after increasing innodb log file size?

    Like innodb buffer pool size or innodb_log_files_in_group?

    Currently I am facing high cpu usage after increasing innodb_log_file_size. Kind of feels like there is some bottleneck between mysql and php-fpm. I see php-fpm causing 70% cpu spike and mysql causing 20-24%.

    0
    Comment actions Permalink
  • Avatar
    Kuzma Ivanov

    Hi Omkar More

    Thanks for the question.

    This guide is for increasing the innodb_log_file_size limit in MySQL, nothing else.

    To troubleshoot high CPU usage caused by MySQL on your server, check out this KB article.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request