Cluster Node on same machine

Hi,

I am running two elasticsearch instances on same machine with following
configuration.

The cluster name

#cluster.name: PAelasticsearch

Path Settings

#path.conf: /path/to/conf
#path.data: /path/to/data
#path.work: /path/to/work
#path.logs: /path/to/logs

Force all memory to be locked, forcing the JVM to never swap

#bootstrap.mlockall: true
#http.port: 9200

Gateway Settings

Controls when to start the initial recovery process when starting a new

cluster

allowing for better reused of existing data during recovery.

#gateway.recover_after_nodes: 1
#gateway.recover_after_time: 5m
#gateway.expected_nodes: 2

Controls the minimum number of master eligible nodes this node should

"see"

in order to operate within the cluster.

Set this to a higher value (2-4) when running more than 2 nodes in the

cluster
#discovery.zen.minimum_master_nodes: 1

The time to wait for ping responses from other nodes when doing node

discovery
#discovery.zen.ping.timeout: 3s

Unicast Discovery (disable multicast)

#discovery.zen.ping.multicast.enabled: false
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

But both of them running independently. I suppose them to run in cluster.

Please advise.

Thanks

Possibly multicast is not enabled on your local machine. You can simply use
unicast discovery even on the same machine, and place in the list of hosts:
"host:9300" and "host:9301" (the second node will use the 9301 port).

On Thu, May 17, 2012 at 12:11 PM, Pulkit Agrawal pulkitdotcom@gmail.comwrote:

Hi,

I am running two elasticsearch instances on same machine with following
configuration.

The cluster name

#cluster.name: PAelasticsearch

Path Settings

#path.conf: /path/to/conf
#path.data: /path/to/data
#path.work: /path/to/work
#path.logs: /path/to/logs

Force all memory to be locked, forcing the JVM to never swap

#bootstrap.mlockall: true
#http.port: 9200

Gateway Settings

Controls when to start the initial recovery process when starting a

new cluster

allowing for better reused of existing data during recovery.

#gateway.recover_after_nodes: 1
#gateway.recover_after_time: 5m
#gateway.expected_nodes: 2

Controls the minimum number of master eligible nodes this node should

"see"

in order to operate within the cluster.

Set this to a higher value (2-4) when running more than 2 nodes in the

cluster
#discovery.zen.minimum_master_nodes: 1

The time to wait for ping responses from other nodes when doing node

discovery
#discovery.zen.ping.timeout: 3s

Unicast Discovery (disable multicast)

#discovery.zen.ping.multicast.enabled: false
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

But both of them running independently. I suppose them to run in cluster.

Please advise.

Thanks