Why did I break RabbitMQ very easily?

V

vaservaser2019-05-29 16:35:59

ubuntu

vaservaser, 2019-05-29 16:35:59

Hello!
I read a lot of good things about RabbitMQ and decided to put it on one of my Ubuntu servers.
Installed, launched, checked, everything works - it receives messages from other machines, and just as well gives them to other machines. Seems to be working as it should.
But then I decided to run a python script that sent messages (base64 in 100Kb) to RabbitMQ dozens of times per second.
For a while everything worked - the second script took messages from the queue, but periodically there were friezes for 1-5 seconds. Then everything worked again.
And at some point, everything broke down. The second script stopped receiving messages from RabbitMQ.
I go to the web panel https://bla.bla.la:15672to see what is there with the rabbit and see messages about 500 errors, there is no control panel - Rabbit does not work.
In general, it does not rise in any way and it came to a complete reinstallation of it.
The question is - is RabbitMQ really so bad and so unreliable that it breaks so easily? This is his main task - to receive messages in the queue and give them.
And then on you, out of the blue, it broke down, I couldn’t process dozens of messages per second normally.

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

S

sokoloid, 2019-05-30
@sokoloid

Actually, this is a design error. Rabbit is not to send files. Queue information with a link to the file, the handler will confirm the processing of the message after downloading the file from the link.

I

Ivan Shumov, 2019-05-30
@inoise

Judging by other comments, you are using the rabbit for other purposes. The Message Broker is so called because it transmits messages. If you want to send a message about a resource, then you only need to send a link to it. Don't fence the garden

R

rino906, 2019-05-30
@rino906

I would not be so categorical about the rabbit, perhaps it broke because you filled up all available RAM and did not set up watermarks (by memory, by disk) + due to the fact that you have rather large messages, you will need to set up preemption messages from RAM to disk. At the same time, I want to note that the option proposed by sokoloid with saving files to temporary storage is more reliable.

F

Fixid, 2019-05-29
@Fixid

A rabbit on one node does not like large messages in a short span. It is necessary to either tune or change the type of queue.