CODEWITHSUNDEEP
symfonydoctrine-orm
user3429660
user3429660

Reputation: 2722

Long running php process with Doctrine

I created a Symfony 3 command that is expected to run for days (or even weeks). It uses Doctrine 2 for reading some initial data and for writing the execution status from time to time. The SQLs are expected to take few milliseconds.

My concern is that the whole process will eventually crash if the MySQL connection closes due to inactivity.

Question: is Doctrine keeping the database connection open between flush calls? Or, is it reconnecting every time flush is called?

Upvotes: 1

Views: 2119

Answers (2)

Mike Doe
Mike Doe

Reputation: 17586

You can simply ping the connection every 1000 seconds, less than MySQL's connection limit.

Best thing to do would be to run a supervising process (eg. supervisord), which would restart the process as soon as your app stops. Then you can simply tell your script to exit before the connection is dropped (as it's a configured value, in MySQL for instance it's the wait_timeout variable). Supervising process will notice your app is dead and will restart it.

Upvotes: -1

tftd
tftd

Reputation: 17042

AFAIK Symfony will open up a connection to the database the first time Doctrine is used in your app and close it when the HTTP request is sent (or if you specifically tell Doctrine to close it). Once connected, Doctrine will have the connection active until you explicitly close it (and will be active before, during and after flush())

In your case you should probably open and close the db connection explicitly when you need it. Something like the following code could solve your problem:

// When you need the DB
/**
 * @var \Doctrine\DBAL\Connection $connection
 */
$connection = $this->get('doctrine')->getConnection();
// check if the connection is still active and if not connect to the db
if(!$connection->isConnected()) {
    $connection->connect();
}
// Your code to update the database goes after this.

your code

// Once you're done with the db update - close the connection.
if($connection->isConnected()) {
    $connection->close(); // close the db connection;
}

This will avoid db connection timeouts and etc, however you should be quite careful with memory leaks if this script will be running as long as you're saying. Using Symfony might not be the best approach to this problem.

Upvotes: 5

Related Questions