php - How does a mysql server restart affect the currently running jobs

Solution:

Depends on how well those php jobs were written. They may hold data until a connection is re-established, they mail fail and 'call for help' or they may fail horribly leaving data in a state of disarray because transaction logic wasn't used.

You could have the best possible outcome, or the worst it entirely depends on how well those php jobs were developed.

Solution:

If you put a bit of code around the actual mysql php calls, you can catch the errors and deal with them.

function mquery( $qry, $lnk ) {
global $dbl;  # your pre-established database link

$result = mysql_query( $qry, $lnk );

if ( $result === false ) {
    $error_msg = mysql_error( $lnk );

    while ( $result === false && @$i < 25 ) {
        $i++;

        $error_no  = mysql_errno( $lnk );

        if      ( $error_no == 1054 ||  # "MySQL Error #1054: Unknown column..."
                     $error_no == 1064 ||  # "You have an error in your SQL syntax" - MAC - May 30, 2012
                     $error_no == 1065 ) { # "Query was empty" 
            break;  # don't loop on errors - it will not succeed
        }
        else if ( $error_no == 1205 ||  # SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction
                     $error_no == 1213 ) { # "Deadlock found when trying to get lock; try restarting transaction" 
            sleep( $i );                 # try sleeping a bit longer to get past the deadlock
        }
        else if ( $error_no == 2003 ||  # SQLSTATE[HY000] [2003] Can't connect to MySQL server
                     $error_no == 2006 ||  # "MySQL server has gone away" -- reconnect 
                     $error_no == 2013 ) { # SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading authorization packet', system error: 0
            sleep( $i );
            if      ( $lnk == $dbl )    { # you may have multiple database links...
                get_dbl();   # re-establish your database link
                $lnk = $dbl;
            }
        }
        else {
            sleep( 1 ); # keeps us from sleeping too long on other errors
        }

        $result = mysql_query( $qry, $lnk );
    }
    echo "\n<!-- MySQL Error #$error_no: '$error_msg' (tried $i times) -->\n";
}

return $result;
Copy code

} // end mquery

If you find that you have other errors that may succeed if you wait a little while, then add them.

For errors that won't succeed no matter how long you wait, add them to the 'break' block of code.

Solution:

Depends how they were written.

In all likelihood, as they're written in PHP, they will get a massive load of errors in the database, which will trigger PHP E_WARNINGs, which the application will completely ignore and generate junk data in its output file, enter an infinite loop, or some other completely useless behaviour.

They certainly won't get killed. However, they might die (which may be reasonable behaviour, provided they can restart and do the right thing).