Inside Meltwater Engineering.

This is the 7th and final part of our blog post series on how we upgraded our Elasticsearch cluster without downtime and with minimal user impact. In this post, we will focus on several of the benefits we have seen after the upgrade and provide more details on how our architecture looks...

Welcome to this sixth part of our adventure of upgrading our Elasticsearch cluster. Until now, we have explained how we structured our work, improved our system to make this migration possible, how we took advantage of this opportunity to make otherwise hard changes, and made sure to keep the system performing well...

This is part 5 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. Due to the large scope of this upgrade, it was clear from the beginning that this project was going to last for at least one year, if not more. This...

This is part 4 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. In part 2 we explained that we decided to do a full reindexing of our entire dataset as part of this Elasticsearch upgrade project. This blog post explains some of...

This is part 3 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. As part of the Elasticsearch Upgrade project, we needed to investigate the search performance improvements between the old and the new versions. Running an older version of Elasticsearch has presented...

This is part 2 in our series on how we upgraded our Elasticsearch cluster without downtime and minimal user impact. As described in Part 1, our requirements were to both provide a smooth transition between two different versions of our system, while still keeping the opportunities for a rollback open. With that...

Back in 2018, now five years ago, we published a blog post describing our 400+ node Elasticsearch cluster. In that post we brought up an important topic: So far, we have elected to not upgrade the cluster. We would like to, but so far there have been more urgent tasks. How we...

We had another Devopsicon — our internal engineering (un)conference. We record most of these company-internal sessions to ensure we can share the knowledge with those who were unable to attend, and to build a knowledge base over time. We have decided to go one step further and share some of these sessions...

A growing Engineering org may reach a point where answering questions that used to be simple have become hard. At least that is true for us! Questions such as: “Who owns this?” “Do we have a component that I can reuse?” “Where are the docs for that API?” This post shares the...