Comment 8 for bug 1328262

Thanks for the email. Making it configurable does seem like a good way to
go. If you propose this in the bug, I'll add support for the idea.

On Wed, Sep 17, 2014 at 5:21 AM, Favoretti <email address hidden> wrote:

> In the past we've asked Percona PS to rebuild our packages in such a way
> that we could override it from /etc/default/mysql, like:
>
> xxx@db003:/var/lib/mysql/journal# cat /etc/default/mysql
> # Default timeout for the server to start
> MYSQL_START_TIMEOUT=180
>
> # Default timeout for the server to stop
> MYSQL_STOP_TIMEOUT=180
>
> If this could be ported upstream - this would be awesome. We have MySQL
> servers with 300GB RAM, just a startup (or a shutdown for that matter)
> takes longer than 5 minutes. Hence, whatever value you hardcode won't
> cut it for edge cases - so why not make it configurable?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1328262
>
> Title:
> init script timeout is too short when resizing logs
>
> Status in Percona Server with XtraDB:
> Triaged
> Status in Percona Server 5.1 series:
> Triaged
> Status in Percona Server 5.5 series:
> Triaged
> Status in Percona Server 5.6 series:
> Triaged
>
> Bug description:
> Currently the init script debian/percona-server-server-5.6.mysql.init
> starts mysqld, then pings it it until it starts. If mysql is not
> accessable after 14 seconds, then the init script will fail.
>
> In MySQL 5.6 the redo logs may be resized during starup, which may
> take longer than 14 seconds.
>
> In my testing (on SSDs), 30 seconds was a sufficient timeout to wait
> for 2GB logs to be generated.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-server/+bug/1328262/+subscriptions
>