Yes, very strange. I really hope to get around this when I upgrade to the
upcoming jgroups version (which is still in alpha stage, so I am waiting).
-shay.banon
On Wed, Mar 31, 2010 at 2:54 AM, Gareth Stokes
gareth@betechnology.com.auwrote:
I did think that was bizarre, and it was only happening on one machine in
the cluster so i can't exactly replicate the issue. just thought i would
document in case anyone else has the same problem.On 30 March 2010 18:09, Shay Banon shay.banon@elasticsearch.com wrote:
I am not sure that the exception you posted on the first mail relates to
the updated configuration since the exception is from the netty layer (the
transport) and jgroups fix is for the discovery layer.In general, you don't have to set the bind_addr, since it should default
to the network.bindHost (assuming both use ipv4/ipv6).-shay.banon
On Tue, Mar 30, 2010 at 8:15 AM, Gareth Stokes <
gareth@betechnology.com.au> wrote:found the problem, ended up being that i didn't have
discovery.jgroups.bind_addr set, here is the config that worked in case
anyone else has the same problem:network:
bindHost: storage1.example.com
publishHost: storage1.example.com
transport:
netty:
port: 9400
http:
netty:
enabled: true
port: 9401
cluster:
name: ExampleIndexer
discovery:
jgroups:
config: tcp
bind_port: 9700
bind_addr: storage1.example.com
tcpping:
initial_hosts: storage1.example.com[9700],storage2.example.com
[9700]On 30 March 2010 13:08, gareth stokes gareth@betechnology.com.auwrote:
Im having a lot of problems getting multiple nodes talking to each
other, for some reason netty keeps on giving me errors.[01:57:20,724][WARN ][transport.netty ] [Alchemy] Exception
caught on netty layer [[id: 0x11fb24d3]]
java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Net.java:30)now i'm sure this has to do with the way i've configured my setup but
for the life of me i can't see what im missing??
this is my config filenetwork :
bindHost : storage1.example.com
publishHost : storage1.example.com
transport :
netty :
port : 9300
cluster :
name : StorageIndexer
discovery :
jgroups :
config : tcp
bind_port : 9400
tcpping :
initial_hosts :
storage1.example.com[9400],storage2.example.com[9400]