Transport Port?


(Edward Giardina) #1

Does anyone know what the port(s) used for the transport client
connections? Our client is in Java and we are receiving the following
stack trace. We have ports 9200 and 9300 open, but we dont know if
there are other ports that need to be open through the firewall. We
are hosting on Rackspace Cloud servers and use Unicast for the ES
standalone instances.

org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:
145)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:
222)


(Shay Banon) #2

9200 is the HTTP port. The Java transport client needs to use port 9300 to
connect to the other nodes.

On Fri, Dec 23, 2011 at 1:23 AM, Edward Giardina
egiardina@servicetask.comwrote:

Does anyone know what the port(s) used for the transport client
connections? Our client is in Java and we are receiving the following
stack trace. We have ports 9200 and 9300 open, but we dont know if
there are other ports that need to be open through the firewall. We
are hosting on Rackspace Cloud servers and use Unicast for the ES
standalone instances.

org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at

org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:
145)
at

org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:
222)


(Edward Giardina) #3

Thanks. Since our ES cluster is setup to use unicast, does that mean
the java api clients also need to be configured to use unicast when
connecting to the cluster?

On Dec 22, 6:48 pm, Shay Banon kim...@gmail.com wrote:

9200 is the HTTP port. The Java transport client needs to use port 9300 to
connect to the other nodes.

On Fri, Dec 23, 2011 at 1:23 AM, Edward Giardina
egiard...@servicetask.comwrote:

Does anyone know what the port(s) used for the transport client
connections? Our client is in Java and we are receiving the following
stack trace. We have ports 9200 and 9300 open, but we dont know if
there are other ports that need to be open through the firewall. We
are hosting on Rackspace Cloud servers and use Unicast for the ES
standalone instances.

org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at

org.elasticsearch.client.transport.TransportClientNodesService.execute(Tran sportClientNodesService.java:
145)
at

org.elasticsearch.client.transport.support.InternalTransportIndicesAdminCli ent.create(InternalTransportIndicesAdminClient.java:
222)


(Shay Banon) #4

Not when you use the TransportClient.

On Fri, Dec 23, 2011 at 1:52 AM, Edward Giardina
egiardina@servicetask.comwrote:

Thanks. Since our ES cluster is setup to use unicast, does that mean
the java api clients also need to be configured to use unicast when
connecting to the cluster?

On Dec 22, 6:48 pm, Shay Banon kim...@gmail.com wrote:

9200 is the HTTP port. The Java transport client needs to use port 9300
to
connect to the other nodes.

On Fri, Dec 23, 2011 at 1:23 AM, Edward Giardina
egiard...@servicetask.comwrote:

Does anyone know what the port(s) used for the transport client
connections? Our client is in Java and we are receiving the following
stack trace. We have ports 9200 and 9300 open, but we dont know if
there are other ports that need to be open through the firewall. We
are hosting on Rackspace Cloud servers and use Unicast for the ES
standalone instances.

org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at

org.elasticsearch.client.transport.TransportClientNodesService.execute(Tran
sportClientNodesService.java:

at

org.elasticsearch.client.transport.support.InternalTransportIndicesAdminCli
ent.create(InternalTransportIndicesAdminClient.java:


(system) #5