Skip to main content

ElasticSearch - The refresh parameter

ElasticSearch is designed as an eventual consistent system, meaning that there is a time gap between the moment a document is indexed and when it becomes available in your search results. This is because ElasticSearch puts documents first in an in-memory buffer. At specified time intervals(by default every second), a refresh operation is triggered that copies the in-memory buffer content to a newly created segment, making the data available for search.

You can start playing around with the refresh interval or trigger the refresh operation manually but in general this is not a good idea.

A better alternative is to use the refresh parameter when inserting/updating your document. This parameter brings you into control when changes made by a request become visible for search.

You have 3 possible options:

  • false: this is the default value, changes to a document are only visible after the next refresh operation
  • true: this forces a refresh in the affected shards
  • wait_for: the request will wait until the next refresh operation completes

As a general recommendation, use false whenever possible, use true only for development purposes and wait_for if you really want to wait for the updated data.

Labels:

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...
Read more

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.
Read more

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...
Read more