Re: TransportClient - Sniffing Issue

2014-04-21 Thread Savva
Jörg, thank you for the reply! hostPort is 9300. For the hostName I have tried two options: 1. to connect to the *public IP address* of the replica machine from my local PC 2. to emulate loopback architecture, e.g. the transport client is allocated on the same replica machine; hostName in this

TransportClient - Sniffing Issue

2014-04-20 Thread savva . khalaman
Hello, I have an ES cluster that consists of two nodes. The first one is explicitly set to be a master and the second serves as a replica. The configuration of the nodes is following: *Master Node:* cluster.name: test-es-cluster node.name: primary1

Re: TransportClient - Sniffing Issue

2014-04-20 Thread Savva
Small typo in the configuration of the replica node. node.master is actually set to false -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: TransportClient - Sniffing Issue

2014-04-20 Thread joergpra...@gmail.com
Which is the hostName/hostPort you connect to? Jörg On Sun, Apr 20, 2014 at 12:08 PM, Savva savva.khala...@gmail.com wrote: Small typo in the configuration of the replica node. node.master is actually set to false -- You received this message because you are subscribed to the Google