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/1b54b0a5-afbf-4c5e-b19d-e169b2aea824%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
