- 🇳🇴Norway steinmb
Move this here. Not sure if this still is an issue? PHP execution timeout can be tricky with `max_execution_time` and `max_input_time` by PHP and other limits introduced by userspace.
According to the first paragraph in this article → , one of the advantages to running migrations within Drush is to avoid the PHP execution timeout.
Drush runs at the command line and is not subject to any time limits (in particular, PHP's max_execution_time does not apply). So, when you start a migration process running via drush, it simply starts up and keeps running until it's done.
My experience seems to contradict that. Running a migration on a content type with 4896 nodes, I got the timeout error twice in two consecutive tries - once at 2637, and then at 2690 (starting over each time). My timeout was set to 180 seconds.
I changed the timeout to 600 seconds, and that migration ran to completion.
Active
6.0
Drush commands
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Move this here. Not sure if this still is an issue? PHP execution timeout can be tricky with `max_execution_time` and `max_input_time` by PHP and other limits introduced by userspace.