[
https://issues.apache.org/jira/browse/METRON-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830008#comment-15830008
]
ASF GitHub Bot commented on METRON-608:
---------------------------------------
Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/408
Is "MySQL should not be installed on a node already running a MySQL
instance" still accurate wrt Ambari MPack? I thought this was fixed. I see it
noted as the 2nd bullet point
[here](https://github.com/mattf-horton/incubator-metron/blob/b5b3a348527c03bc778a5fc5dd0d94ec3a00470b/metron-deployment/README.md#current-limitations).
Would we be able to add that tweak in to this PR since it's so minor, and
it's [semi-]related to the changes made here? I believe the actual fix was a
part of [METRON-410](https://issues.apache.org/jira/browse/METRON-410) (#317)
> 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)
