# Why not use rivers in production?

**URL:** <https://discuss.elastic.co/t/why-not-use-rivers-in-production/15158>\
**Category:** Elasticsearch\
**Created:** [January 9, 2014, 5:15am UTC](https://discuss.elastic.co/t/why-not-use-rivers-in-production/15158 "2014-01-09T05:15:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Warner\_Onstine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warner_onstine/32/1086_2.png) [@Warner\_Onstine](https://discuss.elastic.co/u/Warner_Onstine)\
**Post date:** [January 9, 2014, 5:15am UTC](https://discuss.elastic.co/t/why-not-use-rivers-in-production/15158/1 "2014-01-09T05:15:22Z")

</div>

Getting reintroduced to ES and a co-worker recommended I listen to the  
webinar intro that Drew Raines gave as he mentioned something specific  
about rivers.

Listening through it I heard him say that they (assuming ES) don't  
recommend using rivers in production because it's tied to one node.

Having looked through a lot of the documentation on rivers I do see that  
you can specify which rivers run on which nodes so I wasn't sure what the  
exact implication was of this statement.

Drew? Or anyone else care to comment?

We're getting ready to push all of our data from MongoDB into ES so that we  
can search it and use Kibana for analysis so any insight into this would be  
great, thank you :).

-warner

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAJNTuMAay4fSD%3DaE453Ps2pYFRXcYjeM2TUb718z9na8pYqdBg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAJNTuMAay4fSD%3DaE453Ps2pYFRXcYjeM2TUb718z9na8pYqdBg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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:** [January 9, 2014, 7:18am UTC](https://discuss.elastic.co/t/why-not-use-rivers-in-production/15158/2 "2014-01-09T07:18:43Z")

</div>

A river instance is a singleton in the cluster.  
It means that a river is working only on a single node.

It could be reallocated on another node when the first node fails.

I think that's what Drew meant. Basically, rivers does not scale.

My 2 cents

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr

Le 9 janvier 2014 at 06:15:24, Warner Onstine ([warnero@gmail.com](mailto:warnero@gmail.com)) a écrit:

Getting reintroduced to ES and a co-worker recommended I listen to the webinar intro that Drew Raines gave as he mentioned something specific about rivers.

Listening through it I heard him say that they (assuming ES) don't recommend using rivers in production because it's tied to one node.

Having looked through a lot of the documentation on rivers I do see that you can specify which rivers run on which nodes so I wasn't sure what the exact implication was of this statement.

Drew? Or anyone else care to comment?

We're getting ready to push all of our data from MongoDB into ES so that we can search it and use Kibana for analysis so any insight into this would be great, thank you :).

## -warner

You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAJNTuMAay4fSD%3DaE453Ps2pYFRXcYjeM2TUb718z9na8pYqdBg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAJNTuMAay4fSD%3DaE453Ps2pYFRXcYjeM2TUb718z9na8pYqdBg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/etPan.52ce4d53.749abb43.1449b%40MacBook-Air-de-David.local](https://groups.google.com/d/msgid/elasticsearch/etPan.52ce4d53.749abb43.1449b%40MacBook-Air-de-David.local).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 1:57am UTC](https://discuss.elastic.co/t/why-not-use-rivers-in-production/15158/3 "2017-07-06T01:57:50Z")

</div>


