[
https://issues.apache.org/jira/browse/METRON-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657283#comment-15657283
]
ASF GitHub Bot commented on METRON-563:
---------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/356
PR splits the es_url into 3 fields: es_hosts, es_binary_port, and
es_http_port. The two port fields are defaulted to ES's defaults, so only
hosts needs to be provided by the user on install.
As a note, only the first entry in es_hosts is used for the installed
templates. It was already broken in the case of multiple entries anyway
(because it tried to use the old es_url as a whole, but could be a comma
delimited list), and I didn't want to put in logic around iterating through
servers until one is found and/or retries etc. It seems like a reasonable
requirement to have working servers for something that should be done pretty
soon after install.
To test this, I spun up an Ambari cluster as detailed
https://www.evernote.com/shard/s530/sh/c5551fbd-0ac1-4861-89ce-9c5e37065c52/b13e05f39eaac1a6,
along with a Docker instance of Elasticsearch to hit. The new configs all show
up in the UI and the ports are populated correctly. The service action to
install templates works, and data passes through to indexing using the Bro
topology.
> Ambari Metron service uses incorrect port for installing Elasticsearch
> templates
> --------------------------------------------------------------------------------
>
> Key: METRON-563
> URL: https://issues.apache.org/jira/browse/METRON-563
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.2.1BETA
> Reporter: Justin Leet
> Assignee: Justin Leet
>
> The port entered by the user at install time should be the binary port
> (typically 9300), which is used by the indexing bolt. The installation of
> templates expects the HTTP port for Elasticsearch (typically 9200).
> There are (probably) two options for fixes here:
> 1) Split the ES url and have something like ES Server, ES HTTP port, ES
> Binary port
> 2) Have the template loading go through the binary port. I assume this can
> be done, but I don't know enough about it to say for sure.
> This can be worked around by setting the ES url to <server>:9200, installing
> the templates, and swapping back to <server>:9300.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
