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
Is there a way to kick-start the river in order to force it to start
I'm using Elasticsearch version 0.19.1 with the RabbitMQ River version
1.1.0 and Rabbit MQ version 2.6.1.