GitHub user justinleet opened a pull request:
https://github.com/apache/incubator-metron/pull/367
METRON-522: Need to mandate Client installation on Metron Host
Added metainfo.xml dependency on HBASE_CLIENT. Modified service_advisor to
force colocation of metron_parsers with ZOOKEEPER_CLIENT and HDFS_CLIENT, along
with metron_enrichment colocating with HBASE_CLIENT.
Given that the enrichment master has to be colocated with parsers master in
the current setup, I didn't duplicate the constraints there for brevity,
although if anybody has a preference towards explicitly adding them in code
(beyond the comments mentioning it) I could be pretty easily persuaded.
Tested by spinning a cluster as described in
https://www.evernote.com/shard/s530/sh/c5551fbd-0ac1-4861-89ce-9c5e37065c52/b13e05f39eaac1a6
After setup, the cluster had to be modified to ensure each message could be
hit in the appropriate location (e.g. ensure a given node has Kafka Broker +
HDFS client, but not ZK client, etc.)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/justinleet/incubator-metron METRON-522
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/367.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 #367
----
commit 92c5eddb9519bf28cb4a8dd077042b3b42f0b09c
Author: justinjleet <[email protected]>
Date: 2016-11-21T15:05:22Z
WIP with ZOOKEEPER_SERVER
commit 87d925ca51e6bc0f44d2e6c9f42ca9d9176de4c9
Author: justinjleet <[email protected]>
Date: 2016-11-22T13:41:17Z
Moving to ZK_CLIENT only
commit 15336cb53c0d77f89350715d064f8209108a9df4
Author: justinjleet <[email protected]>
Date: 2016-11-22T13:49:10Z
Slight cleanup to group similar clients
commit 70e3d8d3c68d8475213e262a28b9338cbf517d81
Author: justinjleet <[email protected]>
Date: 2016-11-22T13:50:05Z
Another slight regrouping
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
