[
https://issues.apache.org/jira/browse/METRON-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725452#comment-15725452
]
Justin Leet commented on METRON-609:
------------------------------------
For some additional context, the master only and data configurations only ES
nodes differ in two properties boolean properties (at least for now):
Master:
{code}
node:
data: false
master: true
{code}
These configs are reversed for a Data only node. They can both be true and
it'll be a combined node.
Some other configs may have to change to support this, e.g.
{code}
<property>
<name>gateway_recover_after_data_nodes</name>
<value>3</value>
<description>Recover as long as this many data or master nodes have
joined the cluster.</description>
</property>
{code}
In Ambari service definitions, a cardinality is given for each component (In
this case Master 1+ and Data 3+).
Off the top of my seems like there's a couple approaches to combined nodes
(working within the current setup):
1. Separate component for combined nodes: If we have combined master / data
nodes we want to be able to enforce something like: (1+ C node OR (1+ M AND
3+D)). To the best of my (very) limited knowledge, Ambari doesn't support this.
2. Making Master nodes have a config option for holding data: We could make the
data option for Master be controlled by configuration and set cardinality of D
to 0+. I don't know if a rational cluster definition can be enforced with this
type of setup.
> 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.
> * 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
