Messages are moved to error queuesEdit on GitHub
Some or all messages are not processed and consumed from the queue as normal, but they are moved to their respective error queues, where they stay unprocessed.
The following causes this problem:
- You are exceeding the request entity size restriction of Elasticsearch. In this case, you can find the error message Request entity too large in the RabbitMQ error queues. To check that, see the Solution section.
- Data issues like unmet dependencies. You try to publish a product that references a category that is not in Elasticsearch, or you try to publish information that does not meet the data schema in Redis are frequent causes.
The solution depends on the error the consumer encounters. You can check what the reason is, but getting a message from the error queue, you can find the messages using RabbitMQ UI. The following steps show how this can be done:
- Either the request size needs to be reduced, or your Elasticsearch instance needs to be upscaled. Get in touch with our support, so we can determine the best course of action in your particular case.
- To make the messages consumable, mitigate the error. This is best done in your local development environment as your options to debug the publish and sync process, and the consumption process of the listeners are much better. For this, you can import your staging or production database (that contains the data that you cannot publish correctly) locally, as described in HowTo: Do better deployments.
For submitting the form