amazon web services - EC2 and AMQP: strange TCP issue under load -


Our app is supported by the cluster of EC2 examples, one of them is running RabbitMQ, and all the example messages from the message queue Read and write.

It worked perfectly, until yesterday when we had a significant traffic spike, the messaging system started to fail: the services were able to make the queue, but they could not write or message Could read

It may be from time to time, then all the time.

I rebooted RabbitMQ but it did not help rebooted examples: either did not help. I stopped the whole stack, then started it again and after some time it became normal.

What I can tell (but I'm not sure), the problem failed to communicate with each other (Rabbit MQ sends other TCP messages to a specific port).

I'm worried that it will happen again because I'm not really sure who decided it. And I do not even know where to look.

  • Is communication between AWS throttling / examples limited if there is too much traffic going on?

  • Any other suggestions?

    If RabbitMQ was throttling to producers, then should be visible on the log.

Especially when publishers prevent RabbitMQ from running out of memory or disk space Decides to strangle. As the @ zaq178miami explains, see this link:


Comments

Popular posts from this blog

java - org.apache.http.ProtocolException: Target host is not specified -

java - Gradle dependencies: compile project by relative path -

ruby on rails - Object doesn't support #inspect when used with .include -