[SOLVED] Hi everyone 🤝, I have some configuration for queue: ```// ---------- Queue $conf

giovanni.piemontese

[SOLVED] Hi everyone 🤝,

I have some configuration for queue:

// ---------- Queue
$config[QueueConstants::QUEUE_ADAPTER_CONFIGURATION_DEFAULT] = [
    QueueConfig::CONFIG_QUEUE_ADAPTER => RabbitMqAdapter::class,
    QueueConfig::CONFIG_MAX_WORKER_NUMBER => 12,
];

$config[QueueConstants::QUEUE_ADAPTER_CONFIGURATION][ProductPageSearchConfig::PUBLISH_PRODUCT_ABSTRACT_PAGE][QueueConfig::CONFIG_MAX_WORKER_NUMBER] = 6;

As u see I defined a specific CONFIG_MAX_WORKER_NUMBER for queue PUBLISH_PRODUCT_ABSTRACT_PAGE because it has an high usage of memory (known issue!).
Since this configuration the worker does not start more the task event for this specific queue.
I debugged \Spryker\Zed\Queue\Business\Worker\Worker::startProcesses to see if the right number of maxWorkerNumbers is read and calculated and everything is fine, but no processes are started.

Can anyone help me to understand the problem? Thank u in advance.!!!

UKEP86J66

PUBLISH_PRODUCT_ABSTRACT_PAGE looks like the key for the queue messages - it’s not a queue itself.

UKEP86J66

I think this config only works with the queue names that you see in the RabbitMQ UI queues page, eg sync.search.product

giovanni.piemontese

the queue name is right... and the queue is also there..

UKEP86J66

ah interesting - I’ve not seen the publish queue split like this before

giovanni.piemontese

and the configuration is according the name of queue too...

giovanni.piemontese

I have every queue splitted ... i have ca. 100 queues...

UKEP86J66

Wow

UKEP86J66

I’ve just checked our config for this, it’s slightly different to yours

UKEP86J66

UKEP86J66

Maybe the adapter class is relevant?

giovanni.piemontese

yes.. u are right.. maybe this one... i will try

UKEP86J66

Otherwise I’m out of ideas…

UKEP86J66

Out of interest is the publish queue splitting a Spryker feature, or something custom you have done?

giovanni.piemontese

Spryker standard and some customizations

U01T075RRHD

I you're running into memory issues with RabbitMq, have a look at lazy queues:

https://www.rabbitmq.com/lazy-queues.html

U01T075RRHD

They can reduce the memory footprint significantly

giovanni.piemontese

@U01T075RRHD the problem about memory issue is related to process consumed from spryker to publish the data in the spy_product_abstract_page_search ... Is related to a lot of data loaded and to propel gc too...

what do u mean with rabbitMq memory issue? In RMQ Server Ram used?

giovanni.piemontese

@UKEP86J66 it works!!! Thanks! U saved my day 😄 ...

UKEP86J66

🥳 great to hear!

giovanni.piemontese

I just forgot to specify the adapter class.. in this case the worker was not able to retrieve the message and start the process

UKEP86J66

By the way we had issues with memory for product page search and found there are 2 columns for data in that table. One is for debugging purposes and can be left blank which will certainly reduce the propel memory.

UKEP86J66

I asked about it in Spryker slack but I cannot find the link though 😞

giovanni.piemontese

I think that the structured_data field (this that u left blank) is thought for the refresh command..

U01T075RRHD

@UL65CH0MC Yes, my suggestion targeted RabbitMq memory usage ... so I guess I got you all wrong 😂 . Happy you could work out a solution

giovanni.piemontese

But i can check if the memory usage is related to this field..

giovanni.piemontese

@U01T075RRHD thanks.. But i am interested how did u changed the queues to lazy via spryker... did u overwrite the queue:setup ?

U01T075RRHD

You can provide it in the queue setup using RabbitMqOptionTransfer::setArguments()

U01T075RRHD

https://github.com/spryker/rabbit-mq/blob/master/src/Spryker/Client/RabbitMq/RabbitMqConfig.php#L232

giovanni.piemontese

@U01T075RRHD so ?

    /**
     * @param string $queueName
     * @param string $routingKey
     *
     * @return \Generated\Shared\Transfer\RabbitMqOptionTransfer
     */
    protected function createQueueOptionTransfer($queueName, $routingKey = '')
    {
        $queueOptionTransfer = parent::createQueueOptionTransfer($queueName, $routingKey);

        $queueOptionTransfer->setArguments(['queue-mode' => 'lazy']);

        return $queueOptionTransfer;
    }

Or the arguments should be passed in another way?

U01T075RRHD

It should be x-queue-mode I guess