[
https://issues.apache.org/jira/browse/METRON-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657262#comment-15657262
]
ASF GitHub Bot commented on METRON-563:
---------------------------------------
GitHub user justinleet opened a pull request:
https://github.com/apache/incubator-metron/pull/356
METRON-563: Ambari Metron service uses incorrect port for installing
Elasticsearch templates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/justinleet/incubator-metron METRON-563
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/356.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #356
----
commit c5ebc08780ec3a73efe544449eb588296c99f287
Author: justinjleet <[email protected]>
Date: 2016-11-11T14:56:44Z
METRON-563: Ambari Metron service uses incorrect port for installing
Elasticsearch templates
----
> 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)
