Facebook
Twitter
burnley
Regular Pleskian
Guys, I think this one beats my worst expectations: may I ask what is the technical reason for the Plesk updater restarting MySQL as part of a *micro* update? Can you imagine you may have clients with large databases, large InnoDB tablespaces and restarting the services on those servers may take many minutes?
Point in case: on a CentOS 7.4 running 17.5.3 #MU38, upgrading to #40 takes down the 2 most important services we're running Plesk for: www and mail. Thankfully Bind doesn't need the database backend.
What is the justification for restarting mysqld as part of the update?
Thank you Plesk for ruining my day again with yet another poor example of half baked engineering. NOT!
Point in case: on a CentOS 7.4 running 17.5.3 #MU38, upgrading to #40 takes down the 2 most important services we're running Plesk for: www and mail. Thankfully Bind doesn't need the database backend.
What is the justification for restarting mysqld as part of the update?
Thank you Plesk for ruining my day again with yet another poor example of half baked engineering. NOT!
