[rabbitmq-discuss] rabbit cluster keeps crashing

[LoOoD]

Hi, 

Matthew Sackman wrote:
> 
> Hmm. The nodedown simply suggests that Erlang has lost touch with the
> other
> nodes. What kind of a network are you suing - is this a LAN or WAN or...
> and do you see any sort of packet loss with other applications?
> 
> You may want to experiment with lower values of net_ticktime in your
> rabbitmq.config file:
> 
> [{kernel, [{net_ticktime, 5}]}].
> 
> See
> http://ftp.sunet.se/pub/lang/erlang/doc/man/net_kernel.html#set_net_ticktime-1
> for documentation. It could just be that getting the nodes to talk to each
> other more frequently will solve this. On the other hand, that's likely to
> only be a problem if there are large periods of inactivity in the cluster
> -
> is this the case?
> 

Our servers are connected to gige switches and different subnets. The
switches and routers that the servers are connected to are using less then
10% of their capacity. We don't see any other apps having any sort of
network issues.  We send the rabbit cluster about 70 msgs/sec.

Another symptom we've noticed is the beam.smp process using 100% cpu. Is
there any thing we can do, to help track down the exact cause? Some sort of
increase debugging level? We're willing to do anything to figure out what
going on and stabilize it.


-- 
View this message in context: http://old.nabble.com/rabbit-cluster-keeps-crashing-tp28023134p28157770.html
Sent from the RabbitMQ mailing list archive at Nabble.com.