[rabbitmq-discuss] messages stuck using shovel

Andy Gram agram at blackridge.us
Thu Oct 31 18:10:23 GMT 2013


I have a configuration of 3 RabbitMQ nodes; devtop, devmid, devbot. I am implementing a star configuration with devtop as the center of the start. This is a pubsub application over a WAN. Any node can submit a new item to devtop and my publisher application will publish to all nodes, including itself. I am using shovel to instantiate a queue for each node that is bound to a fanout exchange on devtop. The published messages are stuck on devtop as below;

+-------+--------------------------------+-------------+-----------+---------+------------------------+---------------------+--------+----------+----------------+-------------------------+---------------+--------+---------+
| vhost |              name              | auto_delete | consumers | durable | exclusive_consumer_tag |     idle_since      | memory | messages | messages_ready | messages_unacknowledged |     node      | policy | status  |
+-------+--------------------------------+-------------+-----------+---------+------------------------+---------------------+--------+----------+----------------+-------------------------+---------------+--------+---------+
| /     | amq.gen-QXyScDVGCoTv8bhcbrMOrA | False       | 1         | False   |                        | 2013-10-31 10:32:25 | 9456   | 1        | 0              | 1                       | rabbit at devtop |        | running |
| /     | amq.gen-Ya03CVYcY-CEVKOYcSt0Xw | False       | 1         | False   |                        | 2013-10-31 10:32:25 | 9456   | 1        | 0              | 1                       | rabbit at devtop |        | running |
| /     | new_ident_queue                | False       | 1         | True    |                        | 2013-10-31 10:32:28 | 14312  | 0        | 0              | 0                       | rabbit at devtop |        | running |
| /     | pub_idents                     | False       | 0         | True    |                        | 2013-10-31 10:15:52 | 13760  | 0        | 0              | 0                       | rabbit at devtop |        | running |
| /     | refresh_idents                 | False       | 2         | True    |                        | 2013-10-31 10:32:18 | 14192  | 0        | 0              | 0                       | rabbit at devtop |        | running |
| /     | refresh_queue                  | False       | 1         | True    |                        | 2013-10-31 10:32:18 | 13976  | 0        | 0              | 0                       | rabbit at devtop |        | running |
+-------+--------------------------------+-------------+-----------+---------+------------------------+---------------------+--------+----------+----------------+-------------------------+---------------+--------+---------+

The status on devmid is as follows;

+-------+-----------------+-------------+-----------+---------+------------------------+---------------------+--------+----------+----------------+-------------------------+---------------+--------+---------+
| vhost |      name       | auto_delete | consumers | durable | exclusive_consumer_tag |     idle_since      | memory | messages | messages_ready | messages_unacknowledged |     node      | policy | status  |
+-------+-----------------+-------------+-----------+---------+------------------------+---------------------+--------+----------+----------------+-------------------------+---------------+--------+---------+
| /     | ident_updates   | False       | 0         | True    |                        | 2013-10-31 17:32:03 | 21696  | 0        | 0              | 0                       | rabbit at devmid |        | running |
| /     | new_ident_queue | False       | 1         | True    |                        | 2013-10-31 17:32:03 | 21912  | 0        | 0              | 0                       | rabbit at devmid |        | running |
| /     | refresh_idents  | False       | 0         | True    |                        | 2013-10-31 17:32:03 | 21696  | 0        | 0              | 0                       | rabbit at devmid |        | running |
| /     | refresh_queue   | False       | 1         | True    |                        | 2013-10-31 17:32:03 | 21912  | 0        | 0              | 0                       | rabbit at devmid |        | running |
+-------+-----------------+-------------+-----------+---------+------------------------+---------------------+--------+----------+----------------+-------------------------+---------------+--------+---------+

I am expecting shovel from devmid to move the messages from devtop queue to ident_updates queue on devmid. My shovel configuration follows:
{rabbitmq_shovel,
    [ {shovels, [ {ident_pub,
                    [ {sources, [ {broker, "amqp://"}
                        , {declarations, [
                                 {'queue.declare',
                                        [{queue, <<"new_ident_queue">> }
                                        , durable
                                        ]}
                                ]}
                        ]}
                    , {destinations, [ {broker, "amqp://192.168.168.212"}
                        , {declarations, [
                                 {'queue.declare',
                                        [{queue, <<"new_ident_queue">> }
                                        , durable
                                        ]}
                                ]}
                        ]}
                    , {queue, <<"new_ident_queue">>}
                    , {prefetch_count, 1}
                    , {ack_mode, on_confirm}
                    , {publish_properties, [ {delivery_mode, 2} ]}
                    , {reconnect_delay, 5}
                    ]},
                  {ident_sub,
                    [ {destinations, [ {broker, "amqp://"}
                        , {declarations, [
                                {'queue.declare',
                                        [{queue, <<"ident_updates">> }
                                        , durable
                                        ]}
                                ]}
                        ]}
                    , {sources, [ {broker, "amqp://192.168.168.212"}
                        , {declarations, [ {'exchange.declare',
                                [ {exchange, <<"pub_idents">>}
                                        , {type, <<"fanout">>}
                                        ]}
                                , {'queue.declare',
                                        [{queue, <<>> }
                                        , exclusive
                                        ]}
                                , {'queue.bind',
                                        [ {exchange, <<"pub_idents">>}
                                        , {queue,    <<>>}
                                        ]}
                                ]}
                        ]}
                    , {queue, <<>>}
                    , {prefetch_count, 1}
                    , {ack_mode, on_confirm}
                    , {publish_properties, [ {delivery_mode, 2} ]}
                    , {reconnect_delay, 5}
                    ]},
...

My shovel is stuck!! Any help would be appreciated.

Thanks,
Andy


This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's Email System Administrator.


Andy Gram
BlackRidge Technology Inc.
www.blackridge.us<http://www.blackridge.us/>
408-892-4044

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131031/fef5d567/attachment.htm>


More information about the rabbitmq-discuss mailing list