Hi David, Thank you for your advices. It really helped me to solve the issue and make it works. At the end I had to leave these two: discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["10.185.210.54[9300-9400]","10.101.176.236[9300-9400]"]
and to remove: network.publish_host: 255.255.255.255 And it got work finally. What turned to be the biggest problem is what you mentioned at the beginning, missing spaces after ":", missing spaces at the beginning of line and some extra spaces after #. I thought that : is delimiter, and it doesn't have to be followed by space. Strange thing is that if I have such problems in elasticsearch.yml, there is no logs that indicates that there is some problem. It doesn't log anything and can't start elasticsearch, or just ignore wrong properties. Thanks, Zoran On Friday, 10 October 2014 14:11:00 UTC-7, David Pilato wrote: > > Not sure but may be related to public/private IP. > May be debug logs will give you more insights? > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 10 oct. 2014 à 22:40, Zoran Jeremic <[email protected] <javascript:>> > a écrit : > > Hi David, > > Thank you for your quick response. That was great guess about the space > after ":". It was really something that made a problem, so I'm now a step > forward. It seems that it's trying to establish the connection, but there > are a plenty of exceptions stating that Nework is unreachable. Why this > exception if I can telnet between nodes on 9300? > > [2014-10-10 20:22:12,184][WARN ][transport.netty ] [Joey Bailey] > exception caught on transport layer [[id: 0x5541474b]], closing connection > java.net.SocketException: Network is unreachable > at sun.nio.ch.Net.connect0(Native Method) > at sun.nio.ch.Net.connect(Net.java:465) > at sun.nio.ch.Net.connect(Net.java:457) > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) > at > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink.connect(NioClientSocketPipelineSink.java:108) > at > org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:70) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:574) > at > org.elasticsearch.common.netty.channel.Channels.connect(Channels.java:634) > at > org.elasticsearch.common.netty.channel.AbstractChannel.connect(AbstractChannel.java:207) > at > org.elasticsearch.common.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:229) > at > org.elasticsearch.common.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182) > at > org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:705) > at > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:647) > at > org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:615) > at > org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:129) > at > org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:404) > at > org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:134) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > [2014-10-10 20:22:12,185][WARN ][transport.netty ] [Joey Bailey] > exception caught on transport layer [[id: 0x9e80cd79]], closing connection > > On Friday, 10 October 2014 12:21:18 UTC-7, David Pilato wrote: >> >> I might be wrong but may be you should add a space after each ":" char in >> yml file. >> >> It sounds like multicast is not disabled and that ec2 discovery is not >> used. >> >> Some lines should not be added: >> >> Multicast disable >> Unicast list of nodes >> >> HTH >> >> -- >> David ;-) >> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs >> >> Le 10 oct. 2014 à 19:57, Zoran Jeremic <[email protected]> a écrit : >> >> >> Hi guys, >> >> I need an urgent help to setup Elasticsearch cluster on Amazon EC2 >> instances as I have to launch an application within a week. I'm trying this >> for the last three days without success. I tried to follow many >> instructions, created instances all over again and still nothing. I can >> telnet instances on 9300. I added security group ES2 having a port range >> 0-65535 and also individual instances by private IP addresses with range >> 9200-9400. Nodes can't discover each other,and it seems that both nodes are >> created on their own regardless the fact that cluster node info indicates >> that good elasticsearch.yml is used. For example, cluster name is the one I >> added in elasticsearch.yml, but node name is generic one. >> I hope somebody will have some idea if I missed something here. >> >> Here are other details: >> >> My IAM policy is: >> ########################### >> >> { >> "Version": "2012-10-17", >> "Statement": [ >> { >> "Sid": "Stmt1412960658000", >> "Effect": "Allow", >> "Action": [ >> "ec2:DescribeInstances" >> ], >> "Resource": [ >> "*" >> ] >> } >> ] >> } >> >> >> Cluster configurations are as follows: >> ################################################### >> ######################Master node configuration >> >> cluster.name: elasticsearch >> node.name: "Slave_node" >> node.master: false >> >> discovery.ec2.availability_zones: us-east-1 >> discovery.ec2.ping_timeout: 30s >> cloud.aws.protocol:http >> plugin.mandatory:cloud-aws >> discovery.zen.ping.multicast.enabled:false >> discovery.ec2.groups:ES2 >> #discovery.ec2.tag.type:ElasticsearchCluster >> network.publish_host:255.255.255.255 >> discovery.type:ec2 >> cloud.aws.access_key:<myaccesskey> >> cloud.aws.secret_key:<mysecretkey> >> discovery.zen.ping.unicast.hosts:["10.185.210.54[9300-9400]", >> "10.101.176.236[9300-9400]"] >> cloud.node.auto_attributes:true >> >> >> ###############################Slave node configuration >> >> cluster.name: elasticsearch >> node.name: "Slave_node" >> node.master: false >> >> discovery.ec2.availability_zones: us-east-1 >> discovery.ec2.ping_timeout: 30s >> cloud.aws.protocol:http >> plugin.mandatory:cloud-aws >> discovery.zen.ping.multicast.enabled:false >> discovery.ec2.groups:ES2 >> #discovery.ec2.tag.type:ElasticsearchCluster >> network.publish_host:255.255.255.255 >> discovery.type:ec2 >> cloud.aws.access_key:<myaccesskey> >> cloud.aws.secret_key:<mysecretkey> >> discovery.zen.ping.unicast.hosts:["10.185.210.54[9300-9400]", >> "10.101.176.236[9300-9400]"] >> cloud.node.auto_attributes:true >> >> >> >> ############################################################# >> ##############TRACE LOG FROM SLAVE NODE >> [2014-10-10 17:21:30,554][INFO ][node ] [Gabriel the >> Air-Walker] started >> [2014-10-10 >> 17:21:30,554][DEBUG][cluster.service ] [Gabriel the >> Air-Walker] processing [updating local node id]: done applying updated >> cluster_state (version: 3) >> [2014-10-10 17:21:40,504][DEBUG][cluster.service ] [Gabriel the >> Air-Walker] processing [routing-table-updater]: execute >> [2014-10-10 >> 17:21:40,505][DEBUG][cluster.service ] [Gabriel the >> Air-Walker] processing [routing-table-updater]: no change in >> cluster_state >> [2014-10-10 >> 17:21:44,122][DEBUG][plugins ] [Gabriel the Air-Walker] >> [/usr/share/elasticsearch/plugins/cloud-aws/_site] directory does not >> exist. >> [2014-10-10 17:21:44,123][DEBUG][plugins ] >> [Gabriel the Air-Walker] >> [/usr/share/elasticsearch/plugins/mapper-attachments/_site] directory >> does not exist. >> [2014-10-10 17:22:04,288][INFO ][node ] [Gabriel the >> Air-Walker] stopping ... >> [<span style="color: #066;" class= >> >> ... > > -- > 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/5591c760-1a82-46ca-ab22-98fb6982da95%40googlegroups.com > > <https://groups.google.com/d/msgid/elasticsearch/5591c760-1a82-46ca-ab22-98fb6982da95%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/69b2d7a9-0d8c-472b-8c69-2af60d15b501%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
