0

If you are running RabbitMQ in M 2.3/2.4 and have the env.php section set up for amqp:

    'queue' => [
    'amqp' => [
        'host' => '127.0.0.1',
        'port' => '5672',
        'user' => 'abc',
        'password' => 'def',
        'virtualhost' => '/',
        'ssl' => 'false',
        'ssl_options' => [

        ]
    ]
],

do you remove the cron_consumers_runner section from env.php? Or set it to false? Or trim it down to only specific consumers? Just trying to understand the relationship between the 2 sections. A full cron_consumers_runner section may include:

    'cron_consumers_runner' => [
    'cron_run' => true,
    'max_messages' => 20000,
    'consumers' => [
        'product_action_attribute.update',
        'product_action_attribute.website.update',
        'codegeneratorProcessor',
        'exportProcessor',
        'inventory.source.items.cleanup',
        'inventory.mass.update',
        'inventory.reservations.cleanup',
        'inventory.reservations.update',
        'quoteItemCleaner',
        'inventoryQtyCounter',
        'async.operations.all'
    ]
],
0

The cron_consumers_runner config section is not in the env.php by default. That means you have likely chosen a message queueing system when your site was setup. And with RabbitMQ in mind, you want to try a different Messsage system.

  • The obvious way to go about it would be to remove this config so that you can trial RabbitMQ with having any biased in your experiment.
  • also, if you leave both, you may take chance to have both system conflicting with regards to how the messages get dealt with.

Now, these are recommendations that may not be practical if you want to implement RabbitMQ directly in your production environment.

if you'd want to gradually add RabbitMQ in your Magento stack, my suggestion would be to do it the other way round:

  • keep both queueing systems working together but do this first on a dev environment. Once you have the confirmation both works and there is no visible conficts/negative impact, then you would be able to reply at this moment to your own question and keep both on live environment. Again, trialling technologies together has its risks and can create complications that are unwanted on production. But this way would mean you would not need to stop your emails and start them with a new technology.
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.