Skip to main content

Elastic Search–Help! My indices are not cleaned up

Last week, one of the server admins contacted me that the disk of our ElasticSearch instance was filling up quite fast. He asked me if this was normal? :-) Short answer, no. Let's investigate the issue together...

I started by opening up Kibana and opened Stack Management through the menu on the left.

On the Stack Management page, I clicked on Index Management.

Here I can see the list of all indices. I sorted on Storage size and noticed that MetricBeats was causing the issue. That is strange as I know for sure that I had configured a lifecycle policy that would cleanup old data.

But then I noticed that the health of one of the indices is ‘yellow’. Let’s see what causing this by executing the following request:

GET /.ds-metricbeat-8.2.0-2022.12.03-000011/_ilm/explain?human

This returns the following result:

Notice line 24.

The problem was that the index was configured to have at least one replica. As we are running a single node cluster in development, the index will never turn green.

As the index lifecycle policy only kicks in after the index is in good health, no data was purged from the system.

To fix it, I updated the ES settings to use no replicas:

PUT /_settings
{
"index":{
"number_of_replicas": 0  
}
}

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...