News for hackers. Stuff that matters.
Re:Elasticsearch 1.0.0 released by AznHisoka on Wednesday February 12, 2014 @02:07PM (#7226507)
What I've done, and I'm not totally sure if it's a best practice is I've over-allocated the # of shards. So if I think I need 5 shards, I create 50 or 100 shards instead. Then I'll have some app logic to determine the shard a document should go to. Initially all docs will go to shard 0. Then when that's full (around 15 GB of size, depends on your RAM), then I set all docs to go to shard 1. Of course, you'll need to be careful as you dun want duplicate documents in different shards.

The benefit of this is the as your app scales, you'll search only the shards needed. So if you have just 1 shard w/ data, u can tell ElasticSearch to just search in that 1 shard.

Re:Elasticsearch 1.0.0 released by aquadrop on Wednesday February 12, 2014 @07:49PM (#7228599)
So, what happens when you fill up the last shard?
Re:Elasticsearch 1.0.0 released by ddorian43 on Wednesday February 12, 2014 @02:54PM (#7226843)
look: routing_field