[
https://issues.apache.org/jira/browse/METRON-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713171#comment-15713171
]
ASF GitHub Bot commented on METRON-595:
---------------------------------------
Github user JonathanRider commented on the issue:
https://github.com/apache/incubator-metron/pull/379
Just ran it on quickdev where I set the es.host in the global json file to
"node2,node1" where node2 doesn't exist as it is a single node vagrant.
Using my patch, it writes to ES without a problem as it fails to use node2,
so it switches to node1.
I then compiled master and did the same thing and received this error since
node2 doesn't exist and it fails to use the second host.:
2016-12-01 21:41:18.942 o.a.m.w.BulkWriterComponent [ERROR] Failing 5 tuples
org.elasticsearch.client.transport.NoNodeAvailableException: None of the
configured nodes are available:
[{#transport#-1}{10.120.164.190}{node2/10.120.164.190:9300}]
> Elasticsearch Writer only uses One IP Address
> ---------------------------------------------
>
> Key: METRON-595
> URL: https://issues.apache.org/jira/browse/METRON-595
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Jonathan Rider
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The ES writer can take in a comma separated list of ip:port values, but when
> the writer is initialized, it only uses one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)