From b0b24cb4e210437806230ff3c87a111eac3a2943 Mon Sep 17 00:00:00 2001 From: Julian Simioni Date: Sat, 20 Oct 2018 10:01:18 -0400 Subject: [PATCH] Add link to Elasticsearch blog post on shards --- full_planet_considerations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/full_planet_considerations.md b/full_planet_considerations.md index 6297643..ce59055 100644 --- a/full_planet_considerations.md +++ b/full_planet_considerations.md @@ -38,8 +38,8 @@ used to perform actual geocoding. ### Shard count -Historically, Mapzen Search has used 24 Elasticsearch shards for its builds. However, our latest -guidance from the Elasticsearch team is that shards should be no larger than 50GB, but otherwise +Historically, Mapzen Search has used 24 Elasticsearch shards for its builds. However, the latest +[guidance from the Elasticsearch team](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) is that shards should be no larger than 50GB, but otherwise having as few shards as possible is best. At [geocode.earth](https://geocode.earth) we are experimenting with 12 shard builds, and may eventually move to 6. We would appreciate performance feedback from anyone doing large builds.