[
https://issues.apache.org/jira/browse/METRON-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837347#comment-15837347
]
ASF GitHub Bot commented on METRON-608:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/408
Hi @dlyle65535 , from a design perspective, I totally agree that we should
have a single MPack that works on any size cluster, and I hope to replace both
the 4(+)-node and single-node versions in the future with a more general
solution. I even have a prototype of such. My reasons for proceeding with the
split-off version at this time were entirely pragmatic, due to time pressure:
- I really needed a single-node that works with Ambari, for testing other
PRs.
- I spent several days trying to make Elasticsearch work on a single node
installation, while retaining the generality of the multi-node case, but
couldn't make it work. This chewed up a lot of time.
- I put together a unified Mpack that used two different template files for
Elasticsearch, depending whether it was for a single-node or multi-node
install. That worked just fine, on the surface, but was clearly going to
require in-depth testing of 1, 2, 3, and 4 node cases. I do not currently have
time to thoroughly test all the special cases.
- Doing it this way I only had to test the single-node case, which was
fairly fast.
- Having made one that works, I'd like to make it available to others.
- Now, if it is not accepted into the code, the high rate of change in
metron-deployment will soon obsolete it.
That's pretty much it. It's a throw-away, but not until we do the work of
actually producing the generalized solution and testing it thoroughly. Which I
evaluate as lower priority than a number of other more urgent needs. Thanks.
> Mpack to install a single-node test cluster
> -------------------------------------------
>
> Key: METRON-608
> URL: https://issues.apache.org/jira/browse/METRON-608
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Environment: Linux, Ambari installation
> Reporter: Matt Foley
> Assignee: Matt Foley
> Fix For: Next + 1
>
>
> The current Mpack for Ambari install of Metron fails to correctly install
> Elasticsearch if restricted to a single-node cluster. Yet a single-node
> install of Elasticsearch is certainly feasible, as shown by our quick-dev
> environment.
> This is a short-term fix by providing a completely separate Mpack just for
> the single-node scenario. I'm also opening METRON-609 to enhance the
> existing Mpack to handle the single-node and small-number-of-nodes scenario,
> but that one will require much deeper testing and is likely to take a while
> to complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)