Multiple standalone nodes

[keepcalm]

hi, on version 6.6.1 we already have a single server deployed and i want to bring a new server online as a completely separate instance. How can i do this without the new server trying to form a cluster with the original. Essentially i need 2 dedicated standalone instances

[stephenb (Stephen Brown)]

Hi @keepcalm Welcome to the Community.

First 6.6.1 is very...very..very old and ie EOL in every sense of the term, I would upgrade as soon as you can.

There is a setting to make sure you only ever have a single node see here

discovery.type: single-node

[keepcalm]

thanks for the reply

does this need to be configured on both servers or is it safe to just do it on the new server without changing the existing one? and i take it this is set in the Elasticsearch.yml?

and yes i am aware its old, unfortunately i have inherited this as is and there is an ongoing migration project.

[Christian_Dahlqvist]

You can also make sure the cluster name is unique, which will prevent the nodes joining up.

[keepcalm]

@Christian_Dahlqvist thanks, yeh i have done that so below is what my yml looks like, i also havent added any discovery nodes, so just the below is what settings have been added....i am probably going to use these servers later by adding additional ones to their cluster, so actually is it better to just leave the cluster name unique?:

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

Use a descriptive name for your cluster:

cluster.name: ProdCluster2

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

Use a descriptive name for the node:

node.name: ${HOSTNAME}
node.master: true
node.data: true

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: E:\DATA\ES\data

Path to log files:

path.logs: E:\DATA\ES\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: 0.0.0.0

Set a custom port for HTTP:

http.port: 9200