Serialization failure

[ptrykulich]

Serialization failure

[brandonkelly]

Thanks for reporting that @ptrykulich. It looks like you’re hitting deadlocks due to gap locks. We’ll discuss this internally and see what should be done about it.

In the meantime, you should be able to avoid the errors by only having one queue runner handling these jobs.

[brandonkelly]

Yeah it’s on the list to discuss on our next team call on Monday.

[brandonkelly]

It’s already possible to create a custom queue and push those big jobs to it.

// config/app.php

return [
    // ...
    'bootstrap' => [
        'resaveQueue',
    ],
    'components' => [
        'resaveQueue' => [
            'class' => craft\queue\Queue::class,
        ],
    ],
];

// your module
Craft::$app->resaveQueue->push(new MyResaveJob(/* ... */));

The only caveat is that those jobs won’t show up in the Queue Manager utility (#13347). But all the CLI commands will be available.

php craft help resaveQueue

[ptrykulich]

@brandonkelly

I could use one handler for the queue if I could handle these tasks through a separate runner. Because I need that these big queues did not stop other tasks and this queue was not stopped by others.

I talked about this in Discord with your staff and got a response that I think would be good for me. And get the expected implementation:

// The default Craft queue:
craft queue/listen --channel=default

// On a separate runner:
craft queue/listen --channel=big

• There will be a new config setting where you can define and queue components you want shown in the CP utility
• As long as it is configured there, and implements \craft\queue\QueueInterface, they will both show in the utility.
• Your queue component should register it's own CLI commands, so you have have 2 dedicated listen commands.

But it has not yet been implemented.

[ptrykulich]

Thanks! We will use this solution! But at some point would be great to have deadlock problem sorted.