metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From justinleet <...@git.apache.org>
Subject [GitHub] incubator-metron pull request #223: METRON-386 Create Ambari Service Definit...
Date Mon, 22 Aug 2016 12:59:53 GMT
GitHub user justinleet opened a pull request:

    https://github.com/apache/incubator-metron/pull/223

    METRON-386 Create Ambari Service Definition for Elasticsearch

    https://issues.apache.org/jira/browse/METRON-386
    
    Opening the PR to get community feedback.
    
    Prereq:
    
    Ambari 2.4
    Testing this PR:
    
    *Copy or mount the services and stack contents into the appropriate places on the ambari-server
node. For example:
    ** incubator-metron/metron-deployment/packaging/ambari/src/main/resources/stacks/HDP/2.4/services/ELASTICSEARCH
-> /var/lib/ambari-server/resources/stacks/HDP/2.4/services/ELASTICSEARCH **incubator-metron/metron-deployment/packaging/ambari/src/main/resources/common-services/ELASTICSEARCH
-> /var/lib/ambari-server/resources/common-services/ELASTICSEARCH
    * ES Master eligible nodes will not contain data. Don't colocate master eligible nodes
and data nodes.
    * It's necessary to provide the ES zen_discovery_ping_unicast_hosts.
    
    Limitations / Notes
    * This is based off of Symantec's work at: https://github.com/Symantec/ambari-elasticsearch-service.
 Should I add this into the NOTICE that includes similar contributions?
    * Most configs are used from Symantec's build.  If there are more sane configs, we should
change the defaults (I'm not an ES expert by any means).
    * It would be really nice if zen_discovery_ping_unicast_hosts could be automatically populated
with something sane.  I'm unsure of how to accomplish this with Ambari.
    * Master-eligible nodes are non-data holding nodes that are eligible to be elected master.
Data nodes are, not surprisingly, nodes that only hold data, but are not master-eligible.
It would be nice if thing could be modified to allow master eligible nodes to also hold data
cleanly, but this is left as a further enhancement if needed.
    * A service advisor definition could probably be added to force Ambari to avoid placing
master-eligible and data nodes onto the same node.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/justinleet/incubator-metron metron-elasticsearch

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-metron/pull/223.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 #223
    
----
commit 9861d95e45e5c9b3b39fea0722baafd3bb5d0dc1
Author: justinjleet <justinjleet@gmail.com>
Date:   2016-08-18T13:04:11Z

    Elasticsearch Service in Ambari

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message