RabbitMQ River Not Starting Until Cluster Restarts

Elastic Stack Elasticsearch
1

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!

2

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.comwrote:

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!