Configuration file. Path to data: path error

Elastic Stack Elasticsearch
1

while configuring the latest version of elasticsearch.yml file. the path where we need to store the index cannot be accessed throws an error Masternode not discovered exception. But the same elasticsearch.yml file is working in elasticsearch version 7.3.0 but not in version 7.5.1.

should we need to give the path location or it will take any default location

2

Hi, can u parse ur whole elasticsearch.yml here, which will make it easier to find out the reason?

3

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

https://www.elastic.co/guide/en/elasticsearch/reference/index.html

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

cluster.name: sample

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

node.name: sample

Add custom attributes to the node:

node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

path.data: D:\elasticsearch-7.3.0\data

Path to log files:

path.logs: D:\elasticsearch-7.3.0\logs

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

network.host: xxx.xx.xx.xx

Set a custom port for HTTP:

http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when this node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

discovery.seed_hosts: ["host1", "host2"]

Bootstrap the cluster using an initial set of master-eligible nodes:

cluster.initial_master_nodes: ["node-1", "node-2"]

For more information, consult the discovery and cluster formation module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

#gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

action.destructive_requires_name: true

cluster.routing.allocation.disk.threshold_enabled: false

4

node.name: sample
node.master: true
node.data: true
node.ingest: false

discovery.seed_hosts: [ur other hosts ip address]
discovery.zen.minimum_master_nodes: no of nodes
cluster.initial_master_nodes: sample

but in 7.5 it required 3 master when i tried but u can cross chk with others regarding the minimum master nodes

5

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