Bug #92399

Scheduler tasks are executed in the same php process

Added by DANIEL Rémy 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2020-09-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hi.

The new scheduler:run command runs tasks in a loop.
This can be an issue, because a single php process runs several tasks and those tasks share the same memory.

Example :
I have an issue with Solr indexing tasks: a site A is indexed and loads singletons (Extbase's configuration manager), then the site B gets the configuration manager of the site A! (both sites are on the same TYPO3 instance).

I attached a patch which modifies the scheduler command in order to execute task in subprocesses.


Files

typo3_fix_scheduler_loop.patch (1.25 KB) typo3_fix_scheduler_loop.patch DANIEL Rémy, 2020-09-25 18:43
#1

Updated by DANIEL Rémy 2 months ago

  • File deleted (typo3_fix_scheduler_loop.patch)
#2

Updated by DANIEL Rémy 2 months ago

Patch updated. The process must be executed without any timeout.

#3

Updated by Simon Schaufelberger about 2 months ago

Hi Daniel, uploading patches is not the right way to contribute to the core as somebody still needs to add the code changes to gerrit. Please do that yourself so that you will also get mentioned as contributor ;)

https://docs.typo3.org/m/typo3/guide-contributionworkflow/master/en-us/BugfixingAZ/Index.html#quickstart-create-a-patch

#4

Updated by DANIEL Rémy about 2 months ago

Hi.

I discussed this issue on slack core-dev channel, and I did not get good feedback.
https://typo3.slack.com/archives/C03AM9R17/p1600944189001700

Also, a new project https://github.com/helhum/typo3-crontab is on its way and will on day replace scheduler, if I understood correctly.

Pushing a review to gerrit is time consuming, and the process to get it merged is long and sometimes frustrating.
So in the meantime, I created a issue and attached the patch that works for my usecase.

Also available in: Atom PDF