Hi @BlackbitDevs @Jan-Walther-Basilicom !
DataDirector version 3.9.36 - latest at this moment.
We're struggling with queue not picking up new dataports in queue while very-long-running dataport is still processing.
Steps to reproduce:
Put to queue first long running job
$ queue = new \Blackbit \DataDirectorBundle \model \Queue ();
$ queue ->create ([
'command ' => 'dd:complete 8 ' ,
'triggered_by ' => 'Result callback function of command ... ' ,
]);
Put to queue second job
$ queue = new \Blackbit \DataDirectorBundle \model \Queue ();
$ queue ->create ([
'command ' => 'dd:complete 258 ' ,
'triggered_by ' => 'Result callback function of command ... '
]);
I'm running queue in debug right now, and I can clearly see that while first queue item process is running, queue array is not rebuilt at all:
XDEBUG_TRIGGER =PHPSTORM bin/console data-director:process-queue -v
Demo video with issue being reproduced -
data-director.queue.demo.mp4
Because our dataports can run as long as 24 hours, everything else stalls, and this is hurting business a lot.
Please review :)
Hi @BlackbitDevs @Jan-Walther-Basilicom !
DataDirector version 3.9.36 - latest at this moment.
We're struggling with queue not picking up new dataports in queue while very-long-running dataport is still processing.
Steps to reproduce:
Put to queue first long running job
Put to queue second job
I'm running queue in debug right now, and I can clearly see that while first queue item process is running, queue array is not rebuilt at all:
Demo video with issue being reproduced -
data-director.queue.demo.mp4
Because our dataports can run as long as 24 hours, everything else stalls, and this is hurting business a lot.
Please review :)