TL,DR (Too long, Don’t read.). If you have a dedicated monitoring cluster for your Elasticsearch clusters, you should at least monitor the memory usage of each node. This is very helpful. Instead of fetching the data from the cluster within, we query the monitoring cluster remotely. This watch was created on Elasticsearch with X-Pack v5.4.3. Pay attention, that some values are tweaked and not realistic for production scenarios. The interval for instance is set to 6 hours, since we will execute this watch manually. We also choose 60% as threshold. 75% or 80% would be more realistic for warning scenarios.
Working with Kerberos these days. Some recipes for dealing with Kerberos. There are several open source implementations out there.
Running a Elasticsearch cluster can be an easy task. If you have the need to store data for a long time, but you know the data is infrequently requested, you may think of a hot-warm architecture. This post is a brief summary of my setup for my company at work. At that time Elasticsearch v5.4.1 was running.
To improve page speed on websites, one technique is to deliver less java-script files than leave them in their original state. While it is good for maintenance and separation of concerns to isolate or have a component structure, it isn’t in the way presenting or serving the content. This post demonstrate how to minify, or in the same sense uglify, your java script code with the node package