[
https://issues.apache.org/jira/browse/METRON-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley updated METRON-609:
------------------------------
Description:
The current Mpack for Ambari install of Metron requires that Elasticsearch be
installed with 1+ dedicated Masters and 3+ dedicated Slaves. It does not
support combined master/datanode configuration (non-"dedicated" Master), which
is the recommended way to run a single-node configuration of Elasticsearch; nor
does it allow less than 3 dedicated Slaves, thereby requiring the cluster have
at least 4 nodes.
This jira proposes to enable 1-, 2-, and 3-node clusters to have a working
Elasticsearch install via the Mpack. It will also allow non-dedicated
master/datanodes, which are required for single-node and useful for few-node
clusters.
I intend to also include the following enhancements and fixes:
* Determine whether elastic-sysconfig:data_dir and elastic-site:path_data
should have same default value and if so fix it. (I think they should, and
they don't. Probably there should only be one variable instead of two.)
* Provide Quick Links in Ambari service page for Elasticsearch to the
self-report pages for Elasticsearch health, node list, and other "_cat" status.
May include some "_cluster" status.
* Improve various mouse-over Description fields in the GUI
* Improve the order of fields in the GUI, to group at the beginning the fields
that must be modified or are commonly modified. Possibly separate "basic" and
"advanced" configs.
* Provide a README.md that describes what is going on with the various resource
files in the Mpack src
* Enhance the wiki page for cluster installation, with regard to single-node
install with Mpack.
* Database-preserving upgrade from version 1.0.0.0.
Also see
https://github.com/apache/incubator-metron/tree/master/metron-deployment#current-limitations
for some other known issues. And the documentation in that README.md page is
significantly out of date wrt the Mpack.
was:
The current Mpack for Ambari install of Metron requires that Elasticsearch be
installed with 1+ dedicated Masters and 3+ dedicated Slaves. It does not
support combined master/datanode configuration (non-"dedicated" Master), which
is the recommended way to run a single-node configuration of Elasticsearch; nor
does it allow less than 3 dedicated Slaves, thereby requiring the cluster have
at least 4 nodes.
This jira proposes to enable 1-, 2-, and 3-node clusters to have a working
Elasticsearch install via the Mpack. It will also allow non-dedicated
master/datanodes, which are required for single-node and useful for few-node
clusters.
I intend to also include the following enhancements and fixes:
* Determine whether elastic-sysconfig:data_dir and elastic-site:path_data
should have same default value and if so fix it. (I think they should, and
they don't. Probably there should only be one variable instead of two.)
* Provide Quick Links in Ambari service page for Elasticsearch to the
self-report pages for Elasticsearch health, node list, and other "_cat" status.
May include some "_cluster" status.
* Improve various mouse-over Description fields in the GUI
* Improve the order of fields in the GUI, to group at the beginning the fields
that must be modified or are commonly modified.
* Provide a README.md that describes what is going on with the various resource
files in the Mpack src
* Enhance the wiki page for cluster installation, with regard to single-node
install with Mpack.
> Enhance Mpack to handle single-node and small-cluster installs of
> Elasticsearch
> -------------------------------------------------------------------------------
>
> Key: METRON-609
> URL: https://issues.apache.org/jira/browse/METRON-609
> Project: Metron
> Issue Type: Improvement
> Reporter: Matt Foley
> Assignee: Matt Foley
>
> The current Mpack for Ambari install of Metron requires that Elasticsearch be
> installed with 1+ dedicated Masters and 3+ dedicated Slaves. It does not
> support combined master/datanode configuration (non-"dedicated" Master),
> which is the recommended way to run a single-node configuration of
> Elasticsearch; nor does it allow less than 3 dedicated Slaves, thereby
> requiring the cluster have at least 4 nodes.
> This jira proposes to enable 1-, 2-, and 3-node clusters to have a working
> Elasticsearch install via the Mpack. It will also allow non-dedicated
> master/datanodes, which are required for single-node and useful for few-node
> clusters.
> I intend to also include the following enhancements and fixes:
> * Determine whether elastic-sysconfig:data_dir and elastic-site:path_data
> should have same default value and if so fix it. (I think they should, and
> they don't. Probably there should only be one variable instead of two.)
> * Provide Quick Links in Ambari service page for Elasticsearch to the
> self-report pages for Elasticsearch health, node list, and other "_cat"
> status. May include some "_cluster" status.
> * Improve various mouse-over Description fields in the GUI
> * Improve the order of fields in the GUI, to group at the beginning the
> fields that must be modified or are commonly modified. Possibly separate
> "basic" and "advanced" configs.
> * Provide a README.md that describes what is going on with the various
> resource files in the Mpack src
> * Enhance the wiki page for cluster installation, with regard to single-node
> install with Mpack.
> * Database-preserving upgrade from version 1.0.0.0.
> Also see
> https://github.com/apache/incubator-metron/tree/master/metron-deployment#current-limitations
> for some other known issues. And the documentation in that README.md page
> is significantly out of date wrt the Mpack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
