# Restarting Rivers? **URL:** \ **Category:** Elasticsearch\ **Created:** [November 15, 2010, 2:51pm UTC](https://discuss.elastic.co/t/restarting-rivers/3570 "2010-11-15T14:51:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![phobos182](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phobos182/32/3011_2.png) [@phobos182](https://discuss.elastic.co/u/phobos182)\ **Post date:** [November 15, 2010, 2:51pm UTC](https://discuss.elastic.co/t/restarting-rivers/3570/1 "2010-11-15T14:51:57Z")
I snapshotted my data on my elastic search test cluster, and restarted the nodes. Now the twitter river I have installed is no longer pulling down posts. How do I restart the twitter river? I do not see any documentation for starting / stopping rivers. ---
**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:** [November 15, 2010, 2:58pm UTC](https://discuss.elastic.co/t/restarting-rivers/3570/2 "2010-11-15T14:58:35Z")
Strange..., this should not happen. Do you know if the river was created or not (have a look at the logs, in 0.13, you will have a status API)? You should see a log entry stating that it was created on one of the nodes you have in the cluster. Currently, the only way to restart an existing river is to restart the node it is running on (it will get allocated to another node), but, there should be an API for that, can you open one? -shay.banon On Mon, Nov 15, 2010 at 4:51 PM, Jeremy Carroll [phobos182@gmail.com](mailto:phobos182@gmail.com) wrote: > I snapshotted my data on my Elasticsearch test cluster, and restarted > the nodes. Now the twitter river I have installed is no longer pulling > down posts. How do I restart the twitter river? I do not see any > documentation for starting / stopping rivers. ---
**Author:** ![phobos182](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phobos182/32/3011_2.png) [@phobos182](https://discuss.elastic.co/u/phobos182)\ **Post date:** [November 15, 2010, 3:13pm UTC](https://discuss.elastic.co/t/restarting-rivers/3570/3 "2010-11-15T15:13:08Z")
Thanks for the quick response on this. I was not aware of the update to .13. I will do that this afternoon. I found stack traces in the logs on one of the nodes. The base reason why it was not working was that the 'twitter-river' plugin was not installed on that node. I have fixed this situation by installing the plugin on all nodes in the cluster. Restarting the cluster and removing the work directory loaded the most recent data from the gateway snapshot, and it's back up and running. Thanks for a little kick in the ass for 'user error'. On Nov 15, 8:58 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > Strange..., this should not happen. Do you know if the river was created or > not (have a look at the logs, in 0.13, you will have a status API)? You > should see a log entry stating that it was created on one of the nodes you > have in the cluster. Currently, the only way to restart an existing river is > to restart the node it is running on (it will get allocated to another > node), but, there should be an API for that, can you open one? > > -shay.banon > > On Mon, Nov 15, 2010 at 4:51 PM, Jeremy Carroll [phobos...@gmail.com](mailto:phobos...@gmail.com) wrote: > > > I snapshotted my data on my Elasticsearch test cluster, and restarted > > the nodes. Now the twitter river I have installed is no longer pulling > > down posts. How do I restart the twitter river? I do not see any > > documentation for starting / stopping rivers. ---
**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, 4:16am UTC](https://discuss.elastic.co/t/restarting-rivers/3570/4 "2017-07-06T04:16:31Z")