Elasticsearch Rest-high-level

Elasticsearch Rest-high-level

Opster Team

March 2021


In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

In addition to understanding methods for communicating with Elasticsearch based on HTTP REST endpoints, we recommend you run the Elasticsearch Health Check-Up. It will help you improve your performance by detecting issues and analyzing your endpoints, shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

Run the Elasticsearch check-up to receive recommendations like this:

checklist Run Check-Up
error

The following configuration error was detected on node 123...

error-img

Description

This error can have a severe impact on your system. It's important to understand that it was caused by...

error-img

Recommendation

In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...

1

X-PUT curl -H "Content-Type: application/json" [customized recommendation]

Overview

Rest-high-level is built on top of low-level rest-client and is a method of communicating with Elasticsearch based on HTTP REST endpoints. This concept is majorly popular in the context of a Java-based Elasticsearch client. From day one, Elasticsearch supports transport clients for Java to communicate with Elasticsearch. In version 5.0, a low-level rest-client was released with lots of advantages over the existing transport client such as version independencies, increased stability, and lightweight JAR file libraries.

What it is used for

It is used for communicating with Elasticsearch HTTP REST endpoints in which marshalling and unmarshalling of response objects are handled by the Elasticsearch server itself.


Related log errors to this ES concept


Logger.errortext
Logger.infotext
Logger.warntext
MaxContentLength set to high value; resetting it to 100mb
Unable to apply field level security
High disk watermark exceeded on ; shards will be relocated away from this node
Role uses document and/or field level security; which is not enabled by the current license
high disk watermark exceeded on one or more nodes; rerouting shards
Exception during cleanup of root level blobs
Found stale root level blobs . Cleaning them up
High disk watermark no longer exceeded on . but low disk watermark is still exceeded
Elasticsearch high disk watermark [90%] exceeded on

Run the Check-Up to get a customized report like this:

Analyze your cluster