I think you have a misconception about shard over-allocation and re-indexing, so you should read
https://groups.google.com/d/msg/elasticsearch/49q-_AgQCp8/MRol0t9asEcJ where kimchy explains how over-allocation of shards work. If you have time-series indexes, you need not 20 shards per day, just in fear to be able to stretch out to 20 nodes in the future. That is only true for single, static, non-time-series indexes. With index aliasing and routing applied to time-series data, 1 shard (+1 replica) per day might be enough (maybe some more like 2 or 3, or more replica, it depends on balancing out indexing and search load). For a year with a shard per day, you will end up in 365 shards plus 365 replica shards which is quite a handful, and in theory enough to distribute over 365 nodes. If shards start to get tight on resources, use index aliasing and routing. Or just add nodes, and ES will automatically redistribute the existing shards to become happy again. No re-indexing at all. Jörg -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHoPHqx6GZoPw2QFqjRhc%2BS0AX93fe1WBuwFp_0ZA08NQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
