It seems that it is not enough. The message keeps appearing.
Op dinsdag 31 december 2013 08:43:08 UTC+1 schreef HansPeterSloot: > > No there is only 1 node. > Is is sufficient to remove the # in the elasticsearch.yml before the > following entry: > discovery.zen.ping.multicast.enabled: false > > Regards HansP > > > Op maandag 30 december 2013 20:25:25 UTC+1 schreef Ivan Brusic: >> >> Is/was there another elasticsearch node no the network? If you will only >> have 1 node, you can disable mutlicast discovery. >> >> -- >> Ivan >> >> >> On Mon, Dec 30, 2013 at 3:33 AM, HansPeterSloot <hanspet...@gmail.com>wrote: >> >>> Hi, >>> >>> I have a 1 node elasticsearch cluster which seems to run fine. >>> But I see the following messages in the logfile: >>> [2013-12-30 12:17:35,905][WARN ][cluster.service ] [node1] >>> failed to reconnect to node [node1][I4Wltlc9RSm0jJhumBRtpQ][inet[/ >>> 10.10.10.1:9300]] >>> org.elasticsearch.transport.ConnectTransportException: [node1][inet[/ >>> 10.10.10.1:9300]] connect_timeout[30s] >>> >>> What can I do to get rid of it? >>> >>> Regards HansP >>> >>> -- >>> 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. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/3f9fe20f-6fed-475d-88f3-7441d01ff816%40googlegroups.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f7fa1c06-c099-4c38-83b0-2a5aba30b371%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
