You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Casey Stella (JIRA)" <ji...@apache.org> on 2016/06/10 17:30:21 UTC
[jira] [Commented] (METRON-216) Elasticsearch IP should allow
multiple values
[ https://issues.apache.org/jira/browse/METRON-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324889#comment-15324889 ]
Casey Stella commented on METRON-216:
-------------------------------------
Let's keep this backwards compatible, if possible. If the user specifies a port in the 'es.ip' field in global config (i.e. '127.0.0.1:9200') we should ignore es.port. If es.ip is a list of IPs, then we should use the entire list.
Essentially I'd like to support the following cases:
{
"es.ip" : "127.0.0.1"
,"es.port" : 9200
}
{
"es.ip" : "127.0.0.1:9200"
}
{
"es.ip" : ["127.0.0.1:9200", "192.168.1.1:9200"]
}
> Elasticsearch IP should allow multiple values
> ---------------------------------------------
>
> Key: METRON-216
> URL: https://issues.apache.org/jira/browse/METRON-216
> Project: Metron
> Issue Type: Improvement
> Reporter: David M. Lyle
>
> Currently es.ip and es.port are stored separately in the config and only one is allowed.
> Modify this to accept a list of ip:port pairs so the ES Writer will failover.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)