[rabbitmq-discuss] slave_pids and synchronised_slave_pids not available from the HTTP api?

Wed Jan 4 18:08:29 GMT 2012

I replied a few hours ago:

http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-January/017146.html

Did you not get that?

By the way, here's a first pass at a rabbitmqadmin which fixes the problem:

http://hg.rabbitmq.com/rabbitmq-management/raw-file/83a549d7454c/bin/rabbitmqadmin

Cheers, Simon

On 04/01/12 18:05, Matt Pietrek wrote:
> Resending, as I've not seen any response as of yet, and figured that
> some folks may have come back online after I sent the original message.
>
> If nothing else, simple yes/no to the question in the Subject: would be
> helpful.
>
> Thanks much,
>
> Matt Pietrek
>
> From: Matt Pietrek <mpietrek at skytap.com <mailto:mpietrek at skytap.com>>
> Date: Mon, 02 Jan 2012 11:49:28 -0800
> To: "rabbitmq-discuss at lists.rabbitmq.com
> <mailto:rabbitmq-discuss at lists.rabbitmq.com>"
> <rabbitmq-discuss at lists.rabbitmq.com
> <mailto:rabbitmq-discuss at lists.rabbitmq.com>>
> Cc: Matt Pietrek <mpietrek at skytap.com <mailto:mpietrek at skytap.com>>
> Subject: slave_pids and synchronised_slave_pids not available from the
> HTTP api?
>
> I'm crafting some custom tooling that needs to know about the sync
> status of mirrored queues. Up to this point I've been successfully using
> the HTTP API via the rabbitmqadmin module and been able to get
> everything I need . However, I'm stymied on slave_pids and
> synchronised_slave_pids, which don't seem to come through.
>
> Per the rabbitmqctl cmd-line help, slave_pid and synchronised_slave_pids
> are valid queueinfoitems. Up to this point, queueinfoitem names have
> worked equally well with "rabbitmqadmin list queues"
>
> I've simplified the repro case down to the following; Rabbitmqctl
> displays these fields as expected:
>
> mpietrek at play:~/work/$rabbitmqctl list_queues consumers messages name
> slave_pids synchronised_slave_pids
> Listing queues ...
> 00fake_munger_queue[<rabbit at play2.1.248.0
> <mailto:rabbit at play2.1.248.0>>][<rabbit at play2.1.248.0
> <mailto:rabbit at play2.1.248.0>>]
> 00fake_service_2[<rabbit at play2.1.250.0
> <mailto:rabbit at play2.1.250.0>>][<rabbit at play2.1.250.0
> <mailto:rabbit at play2.1.250.0>>]
> ...done.
>
>
> However, rabbitmqadmin doesn't:
>
> mpietrek at play:~/work/$rabbitmqadmin.py list queues consumers messages
> name slave_pids synchronised_slave_pids
> +-----------+----------+----------------------+------------+-------------------------+
> | consumers | messages | name | slave_pids | synchronised_slave_pids |
> +-----------+----------+----------------------+------------+-------------------------+
> | 0 | 0 | fake_munger_queue | | |
> | 0 | 0 | fake_service_2 | | |
> +-----------+----------+----------------------+------------+-------------------------+
>
> Is this normal/expected? Am I not understanding something?
>
> FWIW, this is using RabbitMQ 2.71 on Ubuntu 10.04.
>
> Thanks,
>
> Matt
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-- 
Simon MacMullen
RabbitMQ, VMware