Nikolaos Tsipas created FLUME-2210:
--------------------------------------

             Summary: UnresolvedAddressException when using multiple hostNames 
in Elasticsearch sink configuration
                 Key: FLUME-2210
                 URL: https://issues.apache.org/jira/browse/FLUME-2210
             Project: Flume
          Issue Type: Bug
          Components: Sinks+Sources
    Affects Versions: v1.4.0
         Environment: Centos 6
Elasticsearch 0.90.5
Lucene 4.4.0
Java 1.7
            Reporter: Nikolaos Tsipas


Hello,

I receive the following error when I define multiple hostnames in elasticsearch 
sink configuration.

*These work*
{code}
a1.sinks.k2.hostNames = 10.0.110.50:9300
{code}
{code}
a1.sinks.k2.hostNames = 10.0.110.51:9300
{code}
*This doesn't*
{code}
a1.sinks.k2.hostNames = 10.0.110.50:9300, 10.0.110.51:9300
{code}

Could be a bug? According to [flume 
documentation|http://flume.apache.org/FlumeUserGuide.html#elasticsearchsink] 
the hostNames property is a "Comma separated list of hostname:port" .

{code}
10 Oct 2013 16:09:14,077 WARN  [elasticsearch[Big Man][generic][T#1]] 
(org.elasticsearch.common.logging.log4j.Log4jESLogger.internalWarn:129)  - [Big 
Man] exception caught on transport layer [[id: 0xac7f61fa]], closing connection
java.nio.channels.UnresolvedAddressException
        at sun.nio.ch.Net.checkAddress(Net.java:127)
        at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:613)
        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:662)
        at 
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:608)
        at 
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:576)
        at 
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:129)
        at 
org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler.sample(TransportClientNodesService.java:305)
        at 
org.elasticsearch.client.transport.TransportClientNodesService$ScheduledNodeSampler.run(TransportClientNodesService.java:284)
        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:724)
{code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to