Deploy a Elasticsearch 8.7.1 cluster with 3 nodes

If you think it is a bug report or you have a technical issue, please answer the following questions. For general questions, you can delete these questions.

**Elasticsearch version:8.7.1

**Server OS version:CENTOS7

Kibana version (if relevant):

Browser version (if relevant):

Browser OS version (if relevant):

Describe the issue:
Here is .yml file

path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
xpack.security.enabled: false
xpack.security.enrollment.enabled: true
xpack.security.http.ssl:
enabled: false
keystore.path: certs/http.p12
xpack.security.transport.ssl:
enabled: true
verification_mode: certificate
keystore.path: certs/transport.p12
truststore.path: certs/transport.p12
#cluster.initial_master_nodes:
#- IP-1
#- IP-2
#IP-3
#http.host: 0.0.0.0
#cluster.name: elasticsearch
node.name: NODE-1
network.host: localhost,IP
http.port: 9200
searchguard.enterprise_modules_enabled: false
thread_pool.write.queue_size: 1000
#node.master: true
#node.data: true
discovery.seed_hosts:
#discovery.zen.ping.unicast.hosts

* IP1
* IP2
* IP3
http.max_content_length: 500mb
indices.query.bool.max_clause_count: 200000
thread_pool.search.size: 50
searchguard.ssl.transport.pemkey_filepath: key.pem
searchguard.ssl.transport.pemcert_filepath: cert.pem
searchguard.ssl.transport.pemtrustedcas_filepath: cacert.pem
searchguard.ssl.transport.enforce_hostname_verification: false
searchguard.ssl.transport.enabled_protocols:
* TLSv1.2
searchguard.ssl.http.pemkey_filepath: key.pem
searchguard.ssl.http.pemcert_filepath: cert.pem
searchguard.ssl.http.pemtrustedcas_filepath: cacert.pem
searchguard.ssl.http.enabled: true
searchguard.ssl.http.enabled_protocols:
* TLSv1.2
searchguard.authcz.admin_dn:
* CN=Server,O=X X X
searchguard.nodes_dn:

---

##Command to create a token run on Centos-7
[root@localhost bin]# ./elasticsearch-create-enrollment-token -s node

ERROR: Failed to determine the health of the cluster.
[root@localhost bin]# pwd
/usr/share/elasticsearch/bin

[root@localhost ~]# curl -XGET -k -u admin:Admin1.# https://IP:9200/_cat/health
1704589901 21:05:01 elasticsearch green 1 0 10 10 0 1 1 0 - 100.0%

Health is totally fine.

Steps to reproduce:
1.
2.
3.

Expected behavior:

Provide configuration:
elasticsearch/config/elasticsearch.yml
elasticsearch/plugins/search-guard-7/sgconfig/sg_config.yml
kibana/config/kibana.yml (if relevant)

Provide logs:
Elasticsearch
Kibana (if relevant)

Screenshots (if relevant):

Errors in browser console (if relevant):

Additional data:

I have asked same question in Elastic search forum , They said post this question in Search Guard forum.
I am not sure how I can deploy a 3 node cluster.
ES is installed in each node up and running .
I am using " search-guard-flx-elasticsearch-plugin-1.4.0-es-8.7.1"

Any help will be appreciated.
Thanks

@Varinder1 Do you see any errors or repeating messages in the Elasticsearch logs?

You’ve disabled this option. It is required to form the cluster at the first start.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.