Hey, Rivers are designed to be a cluster singleton - so they only run on one system. The client object is connected to the local node. It might make more sense to have to have another component in front which aggregates your data - maybe logstash, maybe self-written components...
--Alex On Sat, Dec 21, 2013 at 11:25 PM, Karol Gwaj <[email protected]> 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/0facc47e-39b3-4b10-a7eb-faf847516693%40googlegroups.com > . > For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM_u5QeHxjPdmZ7Ph-s2BdM%2BzabY_-rq93pq08g5vmj3PQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
