i use this in my rabbitmq river setup to ensure that there's always a river up and consuming messages from rabbitmq regardless of whether a rabbitmq or elasticsearch node goes down. on each elasticsearch node a separate river document is created for each rabbitmq cluster node and restricted to run only on itself via allocation.
so the _river index will end up with multiple documents for each elasticsearch node: logger01-1 -> mq01 logger01-2 -> mq02 logger02-1 -> mq01 logger02-2 -> mq02 it works well in my situation, though i have a small cluster. having it puppet-ized helps deal with scaling out new nodes. byron On Monday, December 23, 2013 10:39:11 AM UTC-5, Justin Doles wrote: > > This is as close as you can get: > http://www.elasticsearch.org/guide/en/elasticsearch/rivers/current/index.html#allocation > > > On Saturday, December 21, 2013 5:25:18 PM UTC-5, Karol Gwaj wrote: >> >> Hi, >> >> is there any build-in way to ensure that rivers are equally distributed >> across nodes in the elasticsearch cluster ? >> (i have like 100 rivers pulling data from different sources and i will >> like to avoid situation when they all run on this same node (i want to >> distribute the load across cluster)) >> >> as i understand river will try run on the node on which it was created, >> is it possible (from inside plugin) to force creation of the river on >> another node (the Client object obtained from inside plugin only talks to >> current (local) node) ? >> >> thx for any help, >> >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6b9bcb92-0339-4543-881b-04e868d66df5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
