Cluster setup issue when path.data and path.logs are configured

Elastic Stack Elasticsearch
1

I am trying to setup a 3 node cluster using Elasticsearch-7.17.0 in linux. I have made the following configurations in elasticsearch.yml file of all 3 nodes:

path.data: /some/path/data
path.logs: /some/path/logs
network.host: 0.0.0.0
transport.host: 0.0.0.0
transport.port: 9300
http.port: 9200
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.client_authentication: required
xpack.security.transport.ssl.keystore.path: es-cert.p12
xpack.security.transport.ssl.truststore.path: es-cert.p12
discovery.seed_hosts: ["host1", "host2", "host3"]
cluster.initial_master_nodes: ["node-1", "node-2", "node-3"]

P.S. The configured values of path.data and path.logs are outside of Elasticsearch folder.

With this configuration, when I start each node it is choosing itself as master and doesn't try to contact the other nodes configured in discovery.seed_hosts or cluster.initial_master_nodes.
But, if I just remove path.data and path.logs configurations from elasticsearch.yml file, it's working as expected. Hence I do not understand the reason for this strange behavior. Can anyone help me with this issue?

Thanks in advance.

2

You'd really need to share your logs.

3

Sure. I can share the logs for both working and non-working scenarios. Since the text is quite big, I don't think pasting it here is a good idea. So let me know how you want me to share it. Thanks.

4

Gist/pastebin/etc is fine.

5

Clean up your data path，such as : rm -rf /some/path/data/* ，then start the node

6

Initially, I had setup the instance using minimal security (i.e. just the below security setting in elasticsearch.yml file)

xpack.security.enabled: true

After that, I had done the following:
1)Created a certificate, added the certificate password to keystore in one of the node.
2)Copied elasticsearch.keystore and the certificate from the first node to $ES_HOME\config path of other 2 nodes.
Then I had tried to start Elasticsearch on all nodes and that's when I hit the above error. As casterQ suggested above, I changed the path.data setting to a different folder and things are working as expected.

So, my question is if a node is setup with minimal security initially and later updated to enable basic security can no longer be able to use the initial data folder?

7

That's not correct, you can use the same directory.

8

Thanks for the confirmation. But somehow this didn't work for me. As mentioned, I had initially started the server with single-node settings and later added configurations to elasticsearch.yml to make it a part of a cluster. But even after specifying required cluster configurations, it was not trying to discover other nodes (observed through logs) and electing itself as master. Only when I specified a different data folder path, things started working as expected (i.e. it was trying to discover other nodes). But I didn't face this problem when initially I setup the node with cluster configurations.

9

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