Skip to main content

ElasticSearch– Development vs Production Mode

A lot of people are unaware that ElasticSearch can run in 2 modes; Development and Production Mode. So what is the difference between the 2 modes?

Bootstrap Checks

To explain the difference I first have to talk a little bit about bootstrap checks. During the startup of an ElasticSearch node, it will validate certain ElasticSearch, JVM and system settings and checks if they are safe for the operation of ElasticSearch. 

Development vs. production mode

In previous versions of Elasticsearch, a bootstrap check failure was logged as a warning. Unfortunately users didn’t notice these messages. To solve this ElasticSearch introduced the development and production mode. If Elasticsearch is in development mode, any bootstrap checks that fail appear as warnings in the Elasticsearch log. If Elasticsearch is in production mode, any bootstrap checks that fail will cause Elasticsearch to refuse to start.

By default, Elasticsearch assumes that you are working in development mode.

How to switch?

Ok, now that you understand what the difference is between the 2 modes, it’s time for the next question. How can you switch between the two?

This is completely based on the network settings like network.host.  If your node does not bind transport to an external interface (the default), it is in development mode. When the node does bind transport to an external interface, it is in production mode. Simple as that!

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