The most likely reason for this is due to deadlocks. It seems the latest version of Percona Server may be less graceful in dealing with deadlocks than previous versions. The somewhat quick solution to this is to add the following two lines to your MySQL my.cnf file. It will make the database just slightly less fault tolerant, but should prevent deadlocks due to index locking:
You will have to restart Percona (sudo service mysql restart). It may take a while for it to come back up, depending on the size of your binlogs. Don't get nervous if the restart appears to fail. It's almost certainly due to the binlog conversion from statement format to row format is taking a while to complete.
Just do sudo tail -f /var/lib/mysql/mysql-error.log and watch for a line saying it's ready for connections.
The most likely reason for this is due to deadlocks. It seems the latest version of Percona Server may be less graceful in dealing with deadlocks than previous versions. The somewhat quick solution to this is to add the following two lines to your MySQL my.cnf file. It will make the database just slightly less fault tolerant, but should prevent deadlocks due to index locking:
transaction_isolation = READ-COMMITTED binlog_format = ROW
You will have to restart Percona (sudo service mysql restart). It may take a while for it to come back up, depending on the size of your binlogs. Don't get nervous if the restart appears to fail. It's almost certainly due to the binlog conversion from statement format to row format is taking a while to complete.
Just do sudo tail -f /var/lib/mysql/mysql-error.log and watch for a line saying it's ready for connections.