Hacker News Reader

Thank you. Yes it was a massive project.

I don't want to spoil the other blog posts but we managed to solve almost all of our custom use cases without modifying elasticsearch itself. We still have one custom plugin but only to enhance functionality, not for performance and stability reasons.

View on HN

While I fully understand why you run this thing with 300+ nodes as you do, I have to wonder, just for fun - could you actually fit this whole thing on a single large server? Looks like something with 16 TiB RAM and 2 PiB SSD storage is actually a server you could theoretically buy today?

We feel that ~300 nodes strikes a good balance in the cattle vs pets philosophy.

Going up to i3en.12xlarge (or equivalent) would probably have worked as well.

But after that the impact of loosing just one node would be too big.

Cool! Will stay tuned for the next post :)

Reply on news.ycombinator.com