There may still be similar issues though. If anyone has tips on finding
out when or where there might be firewall or security issues obstructing
communication, please let me know.
Currently we still have problems when the XP node closes elastic search
(making the Windows 7 node master) and then tries to reconnect. The error
logs on the XP show nothing, but the logs on Windows 7 show what is below.
However, if the Windows 7 node is shut down making the XP node the master
again, everything seems to work fine again.
[2014-01-15 16:48:12,778][INFO ][cluster.service ] [NodeHelios]
added
{[NodeDevelopment01][UZmP9gC_Q9es46k6o9OWTw][inet[/XXX.XXX.XXX.XXX:9300]],},
reason: zen-disco-receive(join from
node[[NodeDevelopment01][UZmP9gC_Q9es46k6o9OWTw][inet[/XXX.XXX.XXX.XXX:9300]]])
[2014-01-15 16:48:12,873][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [4] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,876][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [10] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,878][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [6] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,879][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [12] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,887][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [3] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,890][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [2] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,890][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [9] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,891][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [8] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,891][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [5] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,892][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [11] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,893][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [1] and action
[cluster/nodeIndexCreated], resetting
[2014-01-15 16:48:12,894][WARN ][transport.netty ] [NodeHelios]
Message not fully read (request) for [7] and action
[cluster/nodeIndexCreated], resetting
On Wednesday, January 15, 2014 3:51:44 PM UTC-6, [email protected] wrote:
>
> Embarrassing - we had set the program exception in Windows Firewall on the
> Windows 7 computer, but we forgotten that Windows Firewall even existed in
> XP...which apparently it did, way back then. It was supposed to notify
> every time it blocked a program but for whatever reason wasn't notifying
> us, but it seems clear that was the issue as it is working now. Apologies,
> and many thanks Brian.
>
> On Wednesday, January 15, 2014 3:31:23 PM UTC-6, InquiringMind wrote:
>>
>> I guess the usual question need to be answered: Are the Java versions
>> exactly the same on all systems?
>>
>> And just to be sure, are the Elasticsearch versions exactly the same on
>> all systems?
>>
>>
>>> *Does anyone know the issue or any resources that walk through how to
>>> troubleshoot these issues? Everything I read seems to assume these issues
>>> don't exist because ElasticSearch is so easy to get up and running.*
>>>
>>
>> It is, on Solaris, Linux, and Mac OS X. I have never tried running ES on
>> Windows. But a mix of XP and 7.... Maybe this is a case where you might
>> wish to try unicast discovery to isolate Windows networking issues across
>> old and new versions of the OS? Or, try it on the two Windows 7 systems and
>> leave the XP system out of the picture; can you keep them talking to each
>> other?
>>
>> Just some thoughts...
>>
>> Brian
>>
>
--
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/c609015a-6cbb-4e1c-a41c-13a76848590d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
