[rabbitmq-discuss] Node failure for a mirrored queue

[Simon MacMullen]

On 11/02/13 10:00, Бородин Владимир wrote:
> So I suppose there are two problems:
> 1. the timeout tuned by the kernel parameters of erlang (this is better)
> or OS (this is a bit worse because it can affect other applications). Is
> there a way to make it smaller in erlang?

Yes, see http://www.rabbitmq.com/partitions.html

> 2. if the live nodes saw the death of killed node, why commands like
> 'rabbitmqctl cluster_status' don't work? I can understand if the queue
> does not work due to wrong policy for a queue, but it should not affect
> the whole cluster, should it?

They should work *after* the dead node has been detected. Until that 
point the cluster doesn't know it's dead and so just waits for it to 
report its status.

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, VMware