Drew, The Elasticsearch default is to create 5 shards for each index. I would start with this. Typically it is best to actually over-shard, which is to say have more than 1 shard per node per index. There is not really any measurable cost to this and it gives you flexibility in your design as you scale out.
For example, if you start with 5 shards on a single server and then later decide you want to add another machine, Elasticsearch will automatically transfer some of those shards over to the new server, giving you better scalability. If you start with only 1 shard you will not get this benefit. Andrew On Jun 26, 2014, at 8:29 PM, Drew Kutcharian <[email protected]> wrote: > Hey Guys, > > I'm working on an analytics dashboard project where we collect events into > Elasticsearch for clients. Each client could have millions of events per > month. We are thinking of using one index with one shard and one replica per > client. Looking at Logstash, it seems like Logstash creates 1 index, with 1 > shard and 0 replicas per day, so that's where we got the inspiration. We > don't anticipate having more than 1000 "clients". Are there any issues with > this design pattern? > > Thanks, > > Drew > > -- > 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/9DC88022-E37D-4C55-81E6-71A52EC5B466%40venarc.com. > 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/9915D1E3-BF3B-44DF-A060-45FA9FF05C46%40elasticsearch.com. For more options, visit https://groups.google.com/d/optout.
