Just wondering if you have something weird with your firewall settings, especially if you run it under windows.
Hi Jörg ,
The elasticsearch is running as data node (single instance on my computer) and client it's a simple java app with one line of code.
Actually, I don't have any idea what I'm doing wrong as it should be very simple, but I spent a week and didn't find any problem that could cause this issue.
The elasticsearch seems to be started and now I don't see any stop notification as what before, but my java app failed to connect to the elasticsearch.
Thanks.
On Wednesday, November 14, 2012 10:26:49 AM UTC+2, Jörg Prante wrote:
Hi,
there is something on your machine which stops your data node immediately after ist has been started.
[2012-11-12 15:40:13,733][INFO ][node ] [Corbo, Jared] {0.19.9}[11076]: starting ...
[2012-11-12 15:40:17,345][INFO ][cluster.service ] [Corbo, Jared] new_master [Corbo, Jared][QJqeSKH0QVWuMIOJyAZFDQ][inet[/10.26.180.190:9300]], reason: zen-disco-join (elected_as_master)
[2012-11-12 15:40:17,739][INFO ][node ] [Corbo, Jared] {0.19.9}[11076]: started
[2012-11-12 15:40:17,776][INFO ][node ] [Corbo, Jared] {0.19.9}[11076]: stopping ...
Next, another node comes up, but this node seems to be a client node.
[2012-11-12 15:40:33,030][INFO ][node ] [Piper] {0.19.9}[8136]: starting ...
[2012-11-12 15:40:36,302][INFO ][cluster.service ] [Piper] new_master [Piper][SYnQFrA_RwSXoBX9Tc9-Rw][inet[/10.26.180.190:9300]], reason: zen-disco-join (elected_as_master)
[2012-11-12 15:40:36,354][DEBUG][transport.netty ] [Piper] connected to node [[Piper][SYnQFrA_RwSXoBX9Tc9-Rw][inet[/10.26.180.190:9300]]]
[2012-11-12 15:40:36,469][INFO ][node ] [Piper] {0.19.9}[8136]: started
[2012-11-12 15:42:56,299][DEBUG][transport.netty ] [Piper] disconnected from [[Piper][SYnQFrA_RwSXoBX9Tc9-Rw][inet[/10.26.180.190:9300]]]
You see, you always start one node at a time, no node detects each other. They all use same address and port 10.26.180.190:9300. Starting and stopping one node after each other can't work. Check if you can set up a server node which stays active, and then connect with a client node, which can be recognized by using a different port than 9300 (it should be 9301 since 9300 is allocated).
Jörg
On Monday, November 12, 2012 9:37:07 PM UTC+1, slavag wrote:
Hi, Jörg
I attached log file from the elasticsearch run.
Thanks,
On Monday, November 12, 2012 10:08:08 AM UTC+2, Jörg Prante wrote:
You are not giving us the full log trace with the error cause. Please switch your log level into DEBUG or TRACE mode, restart the ES node again, and try your client to connect. You will see the full error in the logs.
Possible reasons I can think of: network interface setup, ES network configuration, cluster name mismatch, zen discovery timeout
Best regards,
Jörg
On Sunday, November 11, 2012 3:06:01 PM UTC+1, slavag wrote:
Hi David,
Actually the elasticsearch is running on the same machine where I'm trying to run java.
The elasticsearch is only one node and it's a master node, so I guess it's a data node.
Thanks.
On Sunday, November 11, 2012 3:52:37 PM UTC+2, David Pilato wrote:
It seems that the other node you are trying to connect to is not up.
That’s the way I understand your stacktrace.
I think that when you use a client node, you must have a running data node elsewhere.
HTH
David
De : elasti...@googlegroups.com [mailto:elasti...@googlegroups.com] De la part de slavag
Envoyé : samedi 10 novembre 2012 23:29
À : elasti...@googlegroups.com
Objet : Java client can't start a node
Hi,
Trying simple java client sample :
Node node = nodeBuilder().client(true).node();
Client client = node.client();
With clean elasticsearch 0.19.9, without any changes to configuration
In the past, it was working fine, but now I'm getting in the elasticsearch console :
[2012-11-11 00:15:41,416][WARN ][discovery.zen.ping.multicast] [Boom Boy] received ping response ping_response{target [[Boom Boy][do472RNfRry9KY5Y-t1vaQ][inet[/10.0.0.10:9300]]], master [[Boom Boy][do472RNfRry9KY5Y-t1vaQ
][inet[/10.0.0.10:9300]]], cluster_name[elasticsearch]} with no matching id [144]
and then in the java :
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:356)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Thanks.
--
--
