search-cli | simple tool to perform web searches | Command Line Interface library

I added below params to docker-compose config & problem solved.

It's not working because you are using the wrong API Key. 😅

But don't worry: these things happen a lot. It certainly happened to me.

The API Key that you are creating is for you to issue REST requests against Elasticsearch Service — which is the entity that governs your Elasticsearch and Kibana clusters.

To make it work, you need to create an API Key from Elasticsearch specifically. To create one, go to the Dev Tools Console and issue the following request:

The error message (in Spanish) says "The system cannot find the specified file." Did you check that java is really installed in the specified path?

Here are two related resources:

• How to install SonarQube with Open JDK 11
• https://community.sonarsource.com/t/java-11-not-detected-although-it-is-installed/14160

it is a bad idea to use external configuration files in elasticsearch plugin. ES provides a mechanism for extending the elasticsearch configuration. all of your custom config should be put in the elasticsearch.yml along with a custom setting registration in the plugin like so:

you must recreate the path with elasticsearch user permission.

If you turn on security, it is mandatory that the nodes talk to each other via SSL, i.e. you need to configure your nodes to encrypt communications between them. So you need to perform a few steps:

Step 1: Generate a node certificate

In this step, there are two options:

A. If you don't have any root certificate authority to sign your certificate, you can create one using bin/elasticsearch-certutil ca (follow the steps explained here). You'll obtain a certificate encoded in PKCS#12 that contains the root CA certificate, the node certificate and the private key.

B. If your organization has a root certificate authority (Digicert, etc), you can create a CSR (certificate signing request) to submit to your root CA. Usually, you'll obtain a certificate encoded in PKCS#7. PS: Let us know if this is the path you're taking because there are a few more steps involved to transform that to PKCS#12.

Note that for testing purposes you can definitely use the same certificate on both nodes, i.e. you don't need to generate one certificate per node.

Step 2: Modify your configuration

Once you have your node certificate (either through option A or B), you can modify the configuration on both nodes by adding the following in your elasticsearch.yml files:

Error message is very clear, that you have not defined the proper config for other threadpools, Please notice the first line of your error msg carefully.

"Suppressed: java.lang.IllegalArgumentException: unknown setting [thread_pool.bulk.queue_size] did you mean any of [thread_pool.get.queue_size, thread_pool.write.queue_size, thread_pool.analyze.queue_size, thread_pool.search.queue_size, thread_pool.listener.queue_size]?",

You have defined bulk queue size as thread_pool.bulk.queue_size, which is not correct and as you can read threadpools in ES , there is no, threadpool for bulk, instead it uses write threadpool for bulk requests, from the same doc, hence chaning this to thread_pool.write.queue_size would work for this config.

write For single-document index/delete/update and bulk requests. Thread pool type is fixed with a size of # of allocated processors, queue_size of 10000. The maximum size for this pool is 1 + # of allocated processors.

Now in order to fix this for bulk, Index and other settings, please verify that you are using the correct names for their configs, threadpools can be obtained from any running ES instance and you can easily construct the corresponding config.

http://localhost:9200/_nodes/stats?pretty gives the all the threadpools and some are listed below.

According to POM Reference, Version Order Specification:

"1-snapshot" < "1" < "1-sp" (qualifier padding)

2.0-SNAPSHOT is less than 2.0, which always was in Maven: snapshot versions are the pre-versions of the next release version.

So, no, 2.0-SNAPSHOT does not lie in [2.0,3.0) (2.0 <= x < 3.0). (1,3.0) (1 < x < 3.0) should do it.

And, there's a typo in your Web Server POM:

There are conflict libraries.

You said in your question that you are using jackson-core-2.10.3.jar

And in your dependency list, I see jackson-core-2.10.3.jar

Two different versions causing the conflict. It could probably be transitive dependency. Exclude the one you don't need.

You can refer another similar forum topic