# RabbitMQ River Not Starting Until Cluster Restarts

**URL:** <https://discuss.elastic.co/t/rabbitmq-river-not-starting-until-cluster-restarts/7389>\
**Category:** Elasticsearch\
**Created:** [April 18, 2012, 6:05pm UTC](https://discuss.elastic.co/t/rabbitmq-river-not-starting-until-cluster-restarts/7389 "2012-04-18T18:05:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christopher\_Miles](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christopher_miles/32/2913_2.png) [@Christopher\_Miles](https://discuss.elastic.co/u/Christopher_Miles)\
**Post date:** [April 18, 2012, 6:05pm UTC](https://discuss.elastic.co/t/rabbitmq-river-not-starting-until-cluster-restarts/7389/1 "2012-04-18T18:05:15Z")

</div>

I'm seeing an issue where a RabbitMQ River is instantiated on my  
Elasticsearch cluster but it does not begin reading messages from the  
RabbitMQ queue. When I inspect the document in the "\_river" index it looks  
correct, I don't see anything wrong with it. After I shutdown the cluster  
and then bring it back up, the river then begins handling messages in the  
queue.

Is there a way to kick-start the river in order to force it to start  
reading messages?

I'm using Elasticsearch version 0.19.1 with the RabbitMQ River version  
1.1.0 and Rabbit MQ version 2.6.1.

Thank you!

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [April 21, 2012, 11:15am UTC](https://discuss.elastic.co/t/rabbitmq-river-not-starting-until-cluster-restarts/7389/2 "2012-04-21T11:15:57Z")

</div>

Can you set the logging to trace on the river and see if you can spot why  
its not started? Does it simply not get started when created?

On Wed, Apr 18, 2012 at 9:05 PM, Christopher Miles [twitch04@gmail.com](mailto:twitch04@gmail.com)wrote:

> I'm seeing an issue where a RabbitMQ River is instantiated on my  
> Elasticsearch cluster but it does not begin reading messages from the  
> RabbitMQ queue. When I inspect the document in the "\_river" index it looks  
> correct, I don't see anything wrong with it. After I shutdown the cluster  
> and then bring it back up, the river then begins handling messages in the  
> queue.
> 
> Is there a way to kick-start the river in order to force it to start  
> reading messages?
> 
> I'm using Elasticsearch version 0.19.1 with the RabbitMQ River version  
> 1.1.0 and Rabbit MQ version 2.6.1.
> 
> Thank you!

---

<div class="post-metadata">

**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, 3:31am UTC](https://discuss.elastic.co/t/rabbitmq-river-not-starting-until-cluster-restarts/7389/3 "2017-07-06T03:31:35Z")

</div>