# RabbitMQ: no queues and state idle when indexing **URL:** \ **Category:** Elasticsearch\ **Created:** [January 22, 2015, 11:27am UTC](https://discuss.elastic.co/t/rabbitmq-no-queues-and-state-idle-when-indexing/21774 "2015-01-22T11:27:55Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![drjz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjz/32/972_2.png) [@drjz](https://discuss.elastic.co/u/drjz)\ **Post date:** [January 22, 2015, 11:27am UTC](https://discuss.elastic.co/t/rabbitmq-no-queues-and-state-idle-when-indexing/21774/1 "2015-01-22T11:27:55Z")
Hi all, I have installed the RabbitMQ plugin and added a user "elasticsearch" with administrator rights in RabbitMQ. The plugin is loaded fine: [2015-01-22 11:33:01,974][INFO][plugins] [node2] loaded [river-rabbitmq], sites [] I created the river with these settings: curl -XPUT '[http://10.99.35.231:9200/\_river/rabbitriver/\_meta](http://10.99.35.231:9200/_river/rabbitriver/_meta)' -d '{ "type" : "rabbitmq", "rabbitmq" : { "host" : "10.99.35.231", "port" : 5672, "user" : "elasticsearch", "pass" : "elasticsearch", "vhost" : "/", "queue" : "elasticsearch", "exchange" : "elasticsearch", "routing\_key" : "elasticsearch", "exchange\_declare" : true, "exchange\_type" : "direct", "exchange\_durable" : true, "queue\_declare" : true, "queue\_bind" : true, "queue\_durable" : true, "queue\_auto\_delete" : false, "heartbeat" : "30m", "qos\_prefetch\_size" : 0, "qos\_prefetch\_count" : 10, "nack\_errors" : true }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms", "ordered" : false } }' echo "" curl -XPUT '[http://10.99.35.231:9200/\_river/\_settings](http://10.99.35.231:9200/_river/_settings)' -d '{ "index" : { "number\_of\_replicas" : 0 } }' However, when I index to ES using the Bulk API, no queues are created and the status stays idle, but the data gets indexed to ES "normally" apparently without using RabbitMQ. I am using the RabbitMQ Web GUI for monitoring. Question: what am I doing wrong here? Thanks! /JZ -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 22, 2015, 2:21pm UTC](https://discuss.elastic.co/t/rabbitmq-no-queues-and-state-idle-when-indexing/21774/2 "2015-01-22T14:21:46Z")
Wondering what you are expecting to see? Rivers are meant to get data from a source, transform to JSON and index to elasticsearch, like an ETL. So you push data in RabbitMQ and you should see data coming into elasticsearch. Are you looking for something else? BTW, you should look at logstash. ## HTH. David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > Le 22 janv. 2015 à 12:27, drjz [juntezhang@gmail.com](mailto:juntezhang@gmail.com) a écrit : > > Hi all, > > I have installed the RabbitMQ plugin and added a user "elasticsearch" with administrator rights in RabbitMQ. > > The plugin is loaded fine: > [2015-01-22 11:33:01,974][INFO][plugins] [node2] loaded [river-rabbitmq], sites > > I created the river with these settings: > > curl -XPUT '[http://10.99.35.231:9200/\_river/rabbitriver/\_meta](http://10.99.35.231:9200/_river/rabbitriver/_meta)' -d '{ > "type" : "rabbitmq", > "rabbitmq" : { > "host" : "10.99.35.231", > "port" : 5672, > "user" : "elasticsearch", > "pass" : "elasticsearch", > "vhost" : "/", > "queue" : "elasticsearch", > "exchange" : "elasticsearch", > "routing\_key" : "elasticsearch", > "exchange\_declare" : true, > "exchange\_type" : "direct", > "exchange\_durable" : true, > "queue\_declare" : true, > "queue\_bind" : true, > "queue\_durable" : true, > "queue\_auto\_delete" : false, > "heartbeat" : "30m", > "qos\_prefetch\_size" : 0, > "qos\_prefetch\_count" : 10, > "nack\_errors" : true > }, > "index" : { > "bulk\_size" : 100, > "bulk\_timeout" : "10ms", > "ordered" : false > } > }' > > echo "" > > curl -XPUT '[http://10.99.35.231:9200/\_river/\_settings](http://10.99.35.231:9200/_river/_settings)' -d '{ > "index" : { > "number\_of\_replicas" : 0 > } > }' > > However, when I index to ES using the Bulk API, no queues are created and the status stays idle, but the data gets indexed to ES "normally" apparently without using RabbitMQ. I am using the RabbitMQ Web GUI for monitoring. > > Question: what am I doing wrong here? > > Thanks! > > /JZ > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAE5063D-3D8C-4885-8F39-07BA54648873%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/CAE5063D-3D8C-4885-8F39-07BA54648873%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![drjz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drjz/32/972_2.png) [@drjz](https://discuss.elastic.co/u/drjz)\ **Post date:** [January 22, 2015, 2:42pm UTC](https://discuss.elastic.co/t/rabbitmq-no-queues-and-state-idle-when-indexing/21774/3 "2015-01-22T14:42:01Z")
I have a similar issue as explained here: [https://github.com/elasticsearch/elasticsearch-river-rabbitmq/issues/74](https://github.com/elasticsearch/elasticsearch-river-rabbitmq/issues/74) What I expect to see is that RabbitMQ will create a queue and show me the messages and what is going on. The solution there is using carriage returns. I have used normal new lines so far with the Bulk API and I really wondering if that explains why RabbitMQ stays idle? /JZ On Thursday, January 22, 2015 at 3:22:20 PM UTC+1, David Pilato wrote: > Wondering what you are expecting to see? > Rivers are meant to get data from a source, transform to JSON and index to > elasticsearch, like an ETL. > > So you push data in RabbitMQ and you should see data coming into > elasticsearch. > > Are you looking for something else? > BTW, you should look at logstash. > > ## HTH. > > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 22 janv. 2015 à 12:27, drjz \<[junte...@gmail.com](mailto:junte...@gmail.com) \\> a > écrit : > > Hi all, > > I have installed the RabbitMQ plugin and added a user "elasticsearch" with > administrator rights in RabbitMQ. > > The plugin is loaded fine: > [2015-01-22 11:33:01,974][INFO][plugins] [node2] loaded > [river-rabbitmq], sites > > I created the river with these settings: > > curl -XPUT '[http://10.99.35.231:9200/\_river/rabbitriver/\_meta](http://10.99.35.231:9200/_river/rabbitriver/_meta)' -d '{ > "type" : "rabbitmq", > "rabbitmq" : { > "host" : "10.99.35.231", > "port" : 5672, > "user" : "elasticsearch", > "pass" : "elasticsearch", > "vhost" : "/", > "queue" : "elasticsearch", > "exchange" : "elasticsearch", > "routing\_key" : "elasticsearch", > "exchange\_declare" : true, > "exchange\_type" : "direct", > "exchange\_durable" : true, > "queue\_declare" : true, > "queue\_bind" : true, > "queue\_durable" : true, > "queue\_auto\_delete" : false, > "heartbeat" : "30m", > "qos\_prefetch\_size" : 0, > "qos\_prefetch\_count" : 10, > "nack\_errors" : true > }, > "index" : { > "bulk\_size" : 100, > "bulk\_timeout" : "10ms", > "ordered" : false > } > }' > > echo "" > > curl -XPUT '[http://10.99.35.231:9200/\_river/\_settings](http://10.99.35.231:9200/_river/_settings)' -d '{ > "index" : { > "number\_of\_replicas" : 0 > } > }' > > However, when I index to ES using the Bulk API, no queues are created and > the status stays idle, but the data gets indexed to ES "normally" > apparently without using RabbitMQ. I am using the RabbitMQ Web GUI for > monitoring. > > Question: what am I doing wrong here? > > Thanks! > > /JZ > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/d9b1a183-71fa-479e-8577-b870254bd71d%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4cb16268-32c8-4b2a-886d-a154205cc0ea%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4cb16268-32c8-4b2a-886d-a154205cc0ea%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:37am UTC](https://discuss.elastic.co/t/rabbitmq-no-queues-and-state-idle-when-indexing/21774/4 "2017-07-06T00:37:14Z")