# Any way to disable the rabbitmq river while ES is starting up? **URL:** \ **Category:** Elasticsearch\ **Created:** [November 8, 2011, 7:37am UTC](https://discuss.elastic.co/t/any-way-to-disable-the-rabbitmq-river-while-es-is-starting-up/5807 "2011-11-08T07:37:20Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Matt1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matt1/32/2986_2.png) [@Matt1](https://discuss.elastic.co/u/Matt1)\ **Post date:** [November 8, 2011, 7:37am UTC](https://discuss.elastic.co/t/any-way-to-disable-the-rabbitmq-river-while-es-is-starting-up/5807/1 "2011-11-08T07:37:20Z")
I have a single node, 1 shard/1 replica setup, and I'm using 0.17.8 with the RabbitMQ river plugin. The thing is, when I restart ES, the river seems to start consuming right away, even though the indices are still getting allocated (I'm not sure what this means yet...). This seems to sometimes corrupt the cluster, thought this could be due to other issues that I'm trying to debug right now. In general, it'd be nice if I could validate that the cluster started up properly before the river starts dumping docs into it for indexing. Is there such a way right now? Cheers! Matt ---
**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 9, 2011, 10:39am UTC](https://discuss.elastic.co/t/any-way-to-disable-the-rabbitmq-river-while-es-is-starting-up/5807/2 "2011-11-09T10:39:34Z")
No, there isn't a way to tell the river to wait and only start indexing when the index it is indexing to is allocated (or at least have enough shards started). It should not cause any corruption though..., thats strange... . You can open an issue for it. On Tue, Nov 8, 2011 at 9:37 AM, Matt [matt.chu@gmail.com](mailto:matt.chu@gmail.com) wrote: > I have a single node, 1 shard/1 replica setup, and I'm using 0.17.8 with > the RabbitMQ river plugin. The thing is, when I restart ES, the river seems > to start consuming right away, even though the indices are still getting > allocated (I'm not sure what this means yet...). This seems to sometimes > corrupt the cluster, thought this could be due to other issues that I'm > trying to debug right now. In general, it'd be nice if I could validate > that the cluster started up properly before the river starts dumping docs > into it for indexing. Is there such a way right now? > > Cheers! > Matt ---
**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:** [November 9, 2011, 11:00am UTC](https://discuss.elastic.co/t/any-way-to-disable-the-rabbitmq-river-while-es-is-starting-up/5807/3 "2011-11-09T11:00:23Z")
BTW, I opened a feature request to suspend a river : > > > As writen in the mailing list : http://elasticsearch-users.115913.n3.nabble.com/…Suspend-a-CouchDB-river-tp2964592p2964592.html > > It’s not possible to suspend a CouchDB river without deleting it. > If I delete it, I will have to restart it from scratch. > By suspending it, I will be able to restart the river from the last sequence number given by \_changes API. > > Thanks, > David. David Le 9 nov. 2011 à 11:39, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > No, there isn't a way to tell the river to wait and only start indexing when the index it is indexing to is allocated (or at least have enough shards started). It should not cause any corruption though..., thats strange... . You can open an issue for it. > > On Tue, Nov 8, 2011 at 9:37 AM, Matt [matt.chu@gmail.com](mailto:matt.chu@gmail.com) wrote: > I have a single node, 1 shard/1 replica setup, and I'm using 0.17.8 with the RabbitMQ river plugin. The thing is, when I restart ES, the river seems to start consuming right away, even though the indices are still getting allocated (I'm not sure what this means yet...). This seems to sometimes corrupt the cluster, thought this could be due to other issues that I'm trying to debug right now. In general, it'd be nice if I could validate that the cluster started up properly before the river starts dumping docs into it for indexing. Is there such a way right now? > > Cheers! > Matt ---
**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:49am UTC](https://discuss.elastic.co/t/any-way-to-disable-the-rabbitmq-river-while-es-is-starting-up/5807/4 "2017-07-06T03:49:21Z")