Cluster_name[elasticsearch]} with no matching id

Henri_van_den_Bulk · July 1, 2013, 5:58pm

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the elastic search node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 1, 2013, 6:03pm

What's strange is that if I remove the builder.client(true); I see two of
these error on the node, but it connects without timeout. What's
different/missing?

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

javanna · July 2, 2013, 8:36am

Hi Henri,
I don't think it connects when you remove the client(true) statement.

If you don't set client(true) while creating the node, your client node
will be master eligible and will hold data, like any other elasticsearch
node, which is usually not what you want for a client node. Also, if there
are network problems, your client node might create its own separate
cluster. This is what's happening in your case when you remove the
client(true) statement: the two nodes don't join the same cluster and the
node created from your java code becomes the master of its own separate
cluster.

When you set client(true) you create your client node with the options
master:false and data:false. That means the client will try to join an
existing cluster with same name. But if there are network problems or
cluster name mismatch, the node won't be able to create its own separate
cluster because it cannot be a master and a cluster must have a master
node. Thus you get the MasterNotDiscoveredException because there's no
master in this separate cluster.

I guess you want to stick to the client(true) and would like your client
node to join your existing cluster.

Hope this helps
Luca

On Monday, July 1, 2013 8:03:08 PM UTC+2, Henri van den Bulk wrote:

What's strange is that if I remove the builder.client(true); I see two of
these error on the node, but it connects without timeout. What's
different/missing?

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 2, 2013, 3:58pm

Hi Luca -

Thanks for the reply. For sure I want to have the client not be a node as
I'm developing a client. However, I continue to see these connection issues
and so my question is why is it not able to connect? I see the following
entries in the Windows Resource Monitor that show that the search node is
up and running. Also, I used telnet connect from a different machine to the
search node on port 9200 and 9300 and both respond.

Image PID Address Port Protocol Firewall Status
java.exe 2812 IPv4 unspecified 9200 TCP Allowed, restricted
java.exe 2812 IPv4 unspecified 9300 TCP Allowed, restricted

I now tried to switch the code to use TransportClient, but that does not
work either:

this.client = new TransportClient()
.addTransportAddress(new InetSocketTransportAddress("localhost",
9200))
.addTransportAddress(new InetSocketTransportAddress("localhost",
9300));

Result:

Jul 02, 2013 9:57:21 AM org.elasticsearch.plugins
INFO: [Aardwolf] loaded , sites
Jul 02, 2013 9:57:27 AM org.elasticsearch.client.transport
INFO: [Aardwolf] failed to get node info for
[#transport#-1][inet[localhost/127.0.0.1:9200]], disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[localhost/127.0.0.1:9200]][cluster/nodes/info] request_id [0] timed
out after [4991ms]
at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Jul 02, 2013 9:57:32 AM org.elasticsearch.client.transport
INFO: [Aardwolf] failed to get node info for
[#transport#-1][inet[localhost/127.0.0.1:9200]], disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[localhost/127.0.0.1:9200]][cluster/nodes/info] request_id [1] timed
out after [4989ms]
at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

How can I diagnose this issue more?

On Tuesday, July 2, 2013 2:36:37 AM UTC-6, Luca Cavanna wrote:

Hi Henri,
I don't think it connects when you remove the client(true) statement.

If you don't set client(true) while creating the node, your client node
will be master eligible and will hold data, like any other elasticsearch
node, which is usually not what you want for a client node. Also, if there
are network problems, your client node might create its own separate
cluster. This is what's happening in your case when you remove the
client(true) statement: the two nodes don't join the same cluster and the
node created from your java code becomes the master of its own separate
cluster.

When you set client(true) you create your client node with the options
master:false and data:false. That means the client will try to join an
existing cluster with same name. But if there are network problems or
cluster name mismatch, the node won't be able to create its own separate
cluster because it cannot be a master and a cluster must have a master
node. Thus you get the MasterNotDiscoveredException because there's no
master in this separate cluster.

I guess you want to stick to the client(true) and would like your client
node to join your existing cluster.

Hope this helps
Luca

On Monday, July 1, 2013 8:03:08 PM UTC+2, Henri van den Bulk wrote:

What's strange is that if I remove the builder.client(true); I see two of
these error on the node, but it connects without timeout. What's
different/missing?

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · July 2, 2013, 4:31pm

If you set a different cluster name, don't forget to set it here as well.

See Elasticsearch Platform — Find real-time answers at scale | Elastic

HTH

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 2 juil. 2013 à 17:58, Henri van den Bulk hvandenbulk@gmail.com a écrit :

Hi Luca -

Thanks for the reply. For sure I want to have the client not be a node as I'm developing a client. However, I continue to see these connection issues and so my question is why is it not able to connect? I see the following entries in the Windows Resource Monitor that show that the search node is up and running. Also, I used telnet connect from a different machine to the search node on port 9200 and 9300 and both respond.

Image PID Address Port Protocol Firewall Status
java.exe 2812 IPv4 unspecified 9200 TCP Allowed, restricted
java.exe 2812 IPv4 unspecified 9300 TCP Allowed, restricted

I now tried to switch the code to use TransportClient, but that does not work either:
  this.client = new TransportClient()
  .addTransportAddress(new InetSocketTransportAddress("localhost", 9200))
  .addTransportAddress(new InetSocketTransportAddress("localhost", 9300));
Result:

Jul 02, 2013 9:57:21 AM org.elasticsearch.plugins
INFO: [Aardwolf] loaded , sites
Jul 02, 2013 9:57:27 AM org.elasticsearch.client.transport
INFO: [Aardwolf] failed to get node info for [#transport#-1][inet[localhost/127.0.0.1:9200]], disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException: [inet[localhost/127.0.0.1:9200]][cluster/nodes/info] request_id [0] timed out after [4991ms]
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Jul 02, 2013 9:57:32 AM org.elasticsearch.client.transport
INFO: [Aardwolf] failed to get node info for [#transport#-1][inet[localhost/127.0.0.1:9200]], disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException: [inet[localhost/127.0.0.1:9200]][cluster/nodes/info] request_id [1] timed out after [4989ms]
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

How can I diagnose this issue more?

On Tuesday, July 2, 2013 2:36:37 AM UTC-6, Luca Cavanna wrote:
Hi Henri,
I don't think it connects when you remove the client(true) statement.

If you don't set client(true) while creating the node, your client node will be master eligible and will hold data, like any other elasticsearch node, which is usually not what you want for a client node. Also, if there are network problems, your client node might create its own separate cluster. This is what's happening in your case when you remove the client(true) statement: the two nodes don't join the same cluster and the node created from your java code becomes the master of its own separate cluster.

When you set client(true) you create your client node with the options master:false and data:false. That means the client will try to join an existing cluster with same name. But if there are network problems or cluster name mismatch, the node won't be able to create its own separate cluster because it cannot be a master and a cluster must have a master node. Thus you get the MasterNotDiscoveredException because there's no master in this separate cluster.

I guess you want to stick to the client(true) and would like your client node to join your existing cluster.

Hope this helps
Luca

On Monday, July 1, 2013 8:03:08 PM UTC+2, Henri van den Bulk wrote:
What's strange is that if I remove the builder.client(true); I see two of these error on the node, but it connects without timeout. What's different/missing?

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:
I'm building a simple Java Client same as mentioned posted under Java client can't start a node. But I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my local machine. Firewall is not blocking connections as all firewalls are shutdown and I have tested the ports.
  NodeBuilder builder = nodeBuilder();	
  builder.client(true);
  // Build and start the node.
  node = builder.node();

  client = node.client();	
On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 2, 2013, 4:39pm

I have everything set to the defaults. I tried your suggesting as well to
explicitly set the clustername, but no luck. On the search node you can see
that it's using the defaults:

C:\tools\elasticsearch-0.90.1>bin\elasticsearch
[2013-07-02 09:45:41,667][INFO ][node ] [Baron Zemo]
{0.90.1}[2812]: initializing ...
[2013-07-02 09:45:42,278][INFO ][plugins ] [Baron Zemo]
loaded , sites [bigdesk, inquisitor, HQ, head]
[2013-07-02 09:45:46,484][INFO ][node ] [Baron Zemo]
{0.90.1}[2812]: initialized
[2013-07-02 09:45:46,485][INFO ][node ] [Baron Zemo]
{0.90.1}[2812]: starting ...
[2013-07-02 09:45:46,595][INFO ][transport ] [Baron Zemo]
bound_address {inet[/0.0.0.0:9300]}, publish_address {inet[/x.x.x.x:9300]}
[2013-07-02 09:45:50,177][INFO ][cluster.service ] [Baron Zemo]
new_master [Baron Zemo][zY-fOHRhSCeVk4pEjGdJWw][inet[/x.x.x.x:9300]],
reason: zen-
disco-join (elected_as_master)
[2013-07-02 09:45:50,205][INFO ][discovery ] [Baron Zemo] *
elasticsearch*/zY-fOHRhSCeVk4pEjGdJWw
[2013-07-02 09:45:50,620][INFO ][http ] [Baron Zemo]
bound_address {inet[/0.0.0.0:9200]}, publish_address {inet[/x.x.x.x:9200]}
[2013-07-02 09:45:50,620][INFO ][node ] [Baron Zemo]
{0.90.1}[2812]: started
[2013-07-02 09:46:05,981][INFO ][gateway ] [Baron Zemo]
recovered [3] indices into cluster_state
[2013-07-02 09:48:14,149][WARN ][discovery.zen.ping.multicast] [Baron Zemo]
received ping response ping_response{target [[Baron
Zemo][zY-fOHRhSCeVk4pEjGdJWw][in
et[/10.143.13.57:9300]]], master [[Baron
Zemo][zY-fOHRhSCeVk4pEjGdJWw][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [1]

On Tuesday, July 2, 2013 10:31:50 AM UTC-6, David Pilato wrote:

If you set a different cluster name, don't forget to set it here as well.

See Elasticsearch Platform — Find real-time answers at scale | Elastic

HTH

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 2 juil. 2013 à 17:58, Henri van den Bulk <hvand...@gmail.com<javascript:>>
a écrit :

Hi Luca -

Thanks for the reply. For sure I want to have the client not be a node as
I'm developing a client. However, I continue to see these connection issues
and so my question is why is it not able to connect? I see the following
entries in the Windows Resource Monitor that show that the search node is
up and running. Also, I used telnet connect from a different machine to the
search node on port 9200 and 9300 and both respond.

Image PID Address Port Protocol Firewall Status
java.exe 2812 IPv4 unspecified 9200 TCP Allowed, restricted
java.exe 2812 IPv4 unspecified 9300 TCP Allowed, restricted

I now tried to switch the code to use TransportClient, but that does not
work either:

this.client = new TransportClient()
.addTransportAddress(new InetSocketTransportAddress("localhost",
9200))
.addTransportAddress(new InetSocketTransportAddress("localhost",
9300));

Result:

Jul 02, 2013 9:57:21 AM org.elasticsearch.plugins
INFO: [Aardwolf] loaded , sites
Jul 02, 2013 9:57:27 AM org.elasticsearch.client.transport
INFO: [Aardwolf] failed to get node info for
[#transport#-1][inet[localhost/127.0.0.1:9200]], disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[localhost/127.0.0.1:9200]][cluster/nodes/info] request_id [0] timed
out after [4991ms]
at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Jul 02, 2013 9:57:32 AM org.elasticsearch.client.transport
INFO: [Aardwolf] failed to get node info for
[#transport#-1][inet[localhost/127.0.0.1:9200]], disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[inet[localhost/127.0.0.1:9200]][cluster/nodes/info] request_id [1] timed
out after [4989ms]
at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

How can I diagnose this issue more?

On Tuesday, July 2, 2013 2:36:37 AM UTC-6, Luca Cavanna wrote:

Hi Henri,
I don't think it connects when you remove the client(true) statement.

If you don't set client(true) while creating the node, your client node
will be master eligible and will hold data, like any other elasticsearch
node, which is usually not what you want for a client node. Also, if there
are network problems, your client node might create its own separate
cluster. This is what's happening in your case when you remove the
client(true) statement: the two nodes don't join the same cluster and the
node created from your java code becomes the master of its own separate
cluster.

When you set client(true) you create your client node with the options
master:false and data:false. That means the client will try to join an
existing cluster with same name. But if there are network problems or
cluster name mismatch, the node won't be able to create its own separate
cluster because it cannot be a master and a cluster must have a master
node. Thus you get the MasterNotDiscoveredException because there's no
master in this separate cluster.

I guess you want to stick to the client(true) and would like your client
node to join your existing cluster.

Hope this helps
Luca

On Monday, July 1, 2013 8:03:08 PM UTC+2, Henri van den Bulk wrote:

What's strange is that if I remove the builder.client(true); I see two
of these error on the node, but it connects without timeout. What's
different/missing?

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

jprante · July 2, 2013, 4:49pm

Do not use port 9200 for Java TransportClient

Jörg

Am 02.07.13 17:58, schrieb Henri van den Bulk:

How can I diagnose this issue more?

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 2, 2013, 4:52pm

I turned on the debugging and I'm seeing this on the search node. It looks
like the client makes a connection, but then disconnects.

This is the search node log when using TransportClient.

[2013-07-02 10:42:58,844][DEBUG][http.netty ] [Caiera] Caught
exception while handling client http traffic, closing connection [id:
0x286957a3, /1
27.0.0.1:2609 => /127.0.0.1:9200]
java.io.IOException: An existing connection was forcibly closed by the
remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:166)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2013-07-02 10:42:58,844][DEBUG][http.netty ] [Caiera] Caught
exception while handling client http traffic, closing connection [id:
0xe3612f1f, /1
27.0.0.1:2608 => /127.0.0.1:9200]
java.io.IOException: An existing connection was forcibly closed by the
remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:166)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

When I now change the client code to use nodeBuilder I see the following on
the search node:

[2013-07-02 10:46:26,148][DEBUG][transport.netty ] [Caiera]
connected to node
[[Aardwolf][GDm3DJCFSbiaohcW0G1vKA][inet[/x.x.x.x:9300]]{client=tru
, data=false}]
[2013-07-02 10:46:26,151][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [1]
[2013-07-02 10:46:27,670][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [1]
[2013-07-02 10:46:29,177][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [2]
[2013-07-02 10:46:30,683][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [2]
[2013-07-02 10:46:32,180][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [3]
[2013-07-02 10:46:33,679][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [3]
[2013-07-02 10:46:35,181][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [4]

On the client I see the following - which seems to indicate that it can't
find the master.

Jul 02, 2013 10:46:56 AM org.elasticsearch.discovery
WARNING: [Aardwolf] waited for 30s and no initial state was set by the
discovery
Jul 02, 2013 10:46:56 AM org.elasticsearch.discovery
INFO: [Aardwolf] elasticsearch/GDm3DJCFSbiaohcW0G1vKA
Jul 02, 2013 10:46:56 AM org.elasticsearch.http
INFO: [Aardwolf] bound_address {inet[/0:0:0:0:0:0:0:0:9200]},
publish_address {inet[/x.x.x.x:9200]}
Jul 02, 2013 10:46:56 AM org.elasticsearch.node
INFO: [Aardwolf] {0.90.1}[9556]: started
Loading....
Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

dadoonet · July 2, 2013, 5:44pm

Don't use .addTransportAddress(new InetSocketTransportAddress("localhost", 9200))
Only 9300 port!

David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 2 juil. 2013 à 18:52, Henri van den Bulk hvandenbulk@gmail.com a écrit :

I turned on the debugging and I'm seeing this on the search node. It looks like the client makes a connection, but then disconnects.

This is the search node log when using TransportClient.

[2013-07-02 10:42:58,844][DEBUG][http.netty ] [Caiera] Caught exception while handling client http traffic, closing connection [id: 0x286957a3, /1
27.0.0.1:2609 => /127.0.0.1:9200]
java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:166)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2013-07-02 10:42:58,844][DEBUG][http.netty ] [Caiera] Caught exception while handling client http traffic, closing connection [id: 0xe3612f1f, /1
27.0.0.1:2608 => /127.0.0.1:9200]
java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:166)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

When I now change the client code to use nodeBuilder I see the following on the search node:

[2013-07-02 10:46:26,148][DEBUG][transport.netty ] [Caiera] connected to node [[Aardwolf][GDm3DJCFSbiaohcW0G1vKA][inet[/x.x.x.x:9300]]{client=tru
, data=false}]
[2013-07-02 10:46:26,151][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [1]
[2013-07-02 10:46:27,670][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [1]
[2013-07-02 10:46:29,177][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [2]
[2013-07-02 10:46:30,683][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [2]
[2013-07-02 10:46:32,180][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [3]
[2013-07-02 10:46:33,679][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [3]
[2013-07-02 10:46:35,181][WARN ][discovery.zen.ping.multicast] [Caiera] received ping response ping_response{target [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master [[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [4]

On the client I see the following - which seems to indicate that it can't find the master.

Jul 02, 2013 10:46:56 AM org.elasticsearch.discovery
WARNING: [Aardwolf] waited for 30s and no initial state was set by the discovery
Jul 02, 2013 10:46:56 AM org.elasticsearch.discovery
INFO: [Aardwolf] elasticsearch/GDm3DJCFSbiaohcW0G1vKA
Jul 02, 2013 10:46:56 AM org.elasticsearch.http
INFO: [Aardwolf] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/x.x.x.x:9200]}
Jul 02, 2013 10:46:56 AM org.elasticsearch.node
INFO: [Aardwolf] {0.90.1}[9556]: started
Loading....
Exception in thread "main" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:
I'm building a simple Java Client same as mentioned posted under Java client can't start a node. But I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my local machine. Firewall is not blocking connections as all firewalls are shutdown and I have tested the ports.
  NodeBuilder builder = nodeBuilder();	
  builder.client(true);
  // Build and start the node.
  node = builder.node();

  client = node.client();	
On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]], cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 2, 2013, 6:15pm

That seems to work. Thanks for the help. Why would the node client
connection not work though?

On Tuesday, July 2, 2013 11:44:22 AM UTC-6, David Pilato wrote:

Don't use .addTransportAddress(new
InetSocketTransportAddress("localhost", 9200))
Only 9300 port!

David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 2 juil. 2013 à 18:52, Henri van den Bulk <hvand...@gmail.com<javascript:>>
a écrit :

I turned on the debugging and I'm seeing this on the search node. It looks
like the client makes a connection, but then disconnects.

This is the search node log when using TransportClient.

[2013-07-02 10:42:58,844][DEBUG][http.netty ] [Caiera]
Caught exception while handling client http traffic, closing connection
[id: 0x286957a3, /1
27.0.0.1:2609 => /127.0.0.1:9200]
java.io.IOException: An existing connection was forcibly closed by the
remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:166)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2013-07-02 10:42:58,844][DEBUG][http.netty ] [Caiera]
Caught exception while handling client http traffic, closing connection
[id: 0xe3612f1f, /1
27.0.0.1:2608 => /127.0.0.1:9200]
java.io.IOException: An existing connection was forcibly closed by the
remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
at sun.nio.ch.IOUtil.read(IOUtil.java:166)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at
org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

When I now change the client code to use nodeBuilder I see the following
on the search node:

[2013-07-02 10:46:26,148][DEBUG][transport.netty ] [Caiera]
connected to node
[[Aardwolf][GDm3DJCFSbiaohcW0G1vKA][inet[/x.x.x.x:9300]]{client=tru
, data=false}]
[2013-07-02 10:46:26,151][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [1]
[2013-07-02 10:46:27,670][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [1]
[2013-07-02 10:46:29,177][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [2]
[2013-07-02 10:46:30,683][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [2]
[2013-07-02 10:46:32,180][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [3]
[2013-07-02 10:46:33,679][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [3]
[2013-07-02 10:46:35,181][WARN ][discovery.zen.ping.multicast] [Caiera]
received ping response ping_response{target
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/10.
43.13.57:9300]]], master
[[Caiera][Fhm9sxcbS4myeJRVKsehzA][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [4]

On the client I see the following - which seems to indicate that it can't
find the master.

Jul 02, 2013 10:46:56 AM org.elasticsearch.discovery
WARNING: [Aardwolf] waited for 30s and no initial state was set by the
discovery
Jul 02, 2013 10:46:56 AM org.elasticsearch.discovery
INFO: [Aardwolf] elasticsearch/GDm3DJCFSbiaohcW0G1vKA
Jul 02, 2013 10:46:56 AM org.elasticsearch.http
INFO: [Aardwolf] bound_address {inet[/0:0:0:0:0:0:0:0:9200]},
publish_address {inet[/x.x.x.x:9200]}
Jul 02, 2013 10:46:56 AM org.elasticsearch.node
INFO: [Aardwolf] {0.90.1}[9556]: started
Loading....
Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 2, 2013, 6:16pm

Thanks that worked

On Tuesday, July 2, 2013 10:49:36 AM UTC-6, Jörg Prante wrote:

Do not use port 9200 for Java TransportClient

Jörg

Am 02.07.13 17:58, schrieb Henri van den Bulk:

How can I diagnose this issue more?

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

jprante · July 2, 2013, 6:20pm

The message "java.io.IOException: An existing connection was forcibly
closed by the remote host" looks like you are on Windows? If so, are you
sure you have enough privileges for the ports you use, or is another
process protecting the network? You said no firewall, but there can be
virus scanners etc.

Jörg

Am 02.07.13 20:16, schrieb Henri van den Bulk:

Thanks that worked

On Tuesday, July 2, 2013 10:49:36 AM UTC-6, Jörg Prante wrote:
Do not use port 9200 for Java TransportClient

Jörg

Am 02.07.13 17:58, schrieb Henri van den Bulk:
> How can I diagnose this issue more?
--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Henri_van_den_Bulk · July 5, 2013, 1:53pm

Thanks everyone that helped with this.

On Monday, July 1, 2013 11:58:10 AM UTC-6, Henri van den Bulk wrote:

I'm building a simple Java Client same as mentioned posted under Java
client can't start a node.https://groups.google.com/forum/#!searchin/elasticsearch/$20cluster_name[elasticsearch]}$20with$20no$20matching$20id/elasticsearch/dI9J3lzaMJY/8vYjN-qYKYIJ But
I did not see a resolution there.

Both the Elasticsearch node instance and the client are running on my
local machine. Firewall is not blocking connections as all firewalls are
shutdown and I have tested the ports.

NodeBuilder builder = nodeBuilder();
builder.client(true);
// Build and start the node.
node = builder.node();
client = node.client();

On the node I keep getting the following logs:

master [[Kick-Ass][r6GYgCbfT46UuuFBguCuAQ][inet[/x.x.x.x:9300]]],
cluster_name[elasticsearch]} with no matching id [21]

The client gets:

Exception in thread "main"
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]
at
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(TransportMasterNodeOperationAction.java:169)
at
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:377)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Cluster_name[elasticsearch]} with no matching id

Don't use .addTransportAddress(new InetSocketTransportAddress("localhost", 9200)) Only 9300 port!

Don't use .addTransportAddress(new InetSocketTransportAddress("localhost", 9200)) Only 9300 port!

Don't use .addTransportAddress(new InetSocketTransportAddress("localhost", 9200))
Only 9300 port!

Don't use .addTransportAddress(new
InetSocketTransportAddress("localhost", 9200))
Only 9300 port!