Just add nodes. That's all :) Jörg
On Mon, Oct 6, 2014 at 10:30 AM, Michael Irwin <[email protected]> wrote: > Also, I would be grateful if someone could point me to some good general > information about this kind of thing. > > On Monday, October 6, 2014 4:28:31 AM UTC-4, Michael Irwin wrote: >> >> I'm using ES for searching for events based on date and geo distance, as >> well as textual content. I'm also using logstash for handling app logging >> and analytics. >> >> I've noticed after I have millions of records from logging/analytics, the >> events search starts slowing down. >> >> I'm currently using just one node (testing all of this out before going >> into production). The event data is currently stored in just one index. >> >> My question is, what is a good way to handle this scenario to prevent >> event searches from becoming slow? Should I use separate nodes just for >> logging/analytics? Should I index the event data differently? >> >> Thanks! >> > -- > 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/a9b5f1d8-28a8-464f-a9fd-21b6f0a61d65%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/a9b5f1d8-28a8-464f-a9fd-21b6f0a61d65%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAKdsXoE9sY7EQ%2BWe-RsTcQMNUv%3DvcDRpi6iCTRhk%2BB%3Dv8%3Dx4VA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
