I already saw that issue some months ago but with Shay, we did not find a way to solve it.
It's related to the twitter river itself, not to rivers in general.
The twitter river failed but does not restart itself.
Twitter : @dadoonet / @elasticsearchfr
Le 31 juil. 2012 à 23:15, Adam Estrada email@example.com a écrit :
Thanks for the feedback. It looks like when the twitter river stops working for any reason, the other instance(s) will not pick it up either. This is what you mentioned. So, how do you recommend making sure the rivers never stop running?
On Tue, Jul 31, 2012 at 4:45 PM, Ivan Brusic firstname.lastname@example.org wrote:
Rivers are run as a single instance per cluster. That is the main
benefit of utilizing a river: the indexing is done at the
cluster-level, so it can continue even with partial node failures.
That said, I have never tested how well a river responds should the
node it is running on goes down.
On Tue, Jul 31, 2012 at 5:36 AM, Adam Estrada email@example.com wrote:
I guess what I am looking for is the best way to prevent failure on my
cluster. I am thinking that I can set up 2 masters and then some data nodes
but I really need to ensure that if data has stopped being collected by one
node, the other one will pick it up and run with it. I noticed yesterday
that both master nodes can't have a river on them. Or maybe its that both
masters can't have a river connected to an index with the same name. Anyone
have thoughts on this?
On Monday, July 30, 2012 5:33:45 PM UTC-4, Adam Estrada wrote:
I am wondering what the default behavior (see title) in my cluster is
supposed to be. I am collecting tweets in a cluster called Twitter. Right
now there are 2 nodes, server1 and server2. If one of these nodes fails, I
would like for the other one to pick up where it left off. Is that the
intended behavior or is there some other mechanism I am missing? I should
note that the index I created has 6 shards and 2 replicas.