Github user anandsubbu commented on the issue:
https://github.com/apache/incubator-metron/pull/315
I did a run with of this PR on a 12-node openstack setup and here are some
observations. Note that this was on a fresh deployment and _not_ one with HDP
already present.
At the outset, the co-location error messages are seen against the Metron
nodes. After a few moments, there is an exclamation against a faulty host with
the error message seen on mouse-over.
1) Against the MySQL server, the error text says "Metron Enrichment Master
must be co-located...". I understand that the primary usage of this node is for
the enrichment, yes. But wanted to know if this text is intentional. Or should
we rename the error to indicate the MySQL node?
2) At the very first time, Metron Parsers node displays the error about
KAFKA_BROKER co-location. Subsequently, once the KAFKA node is added, this
error changes to STORM SUPERVISOR co-location. This is seen to work as
expected.
3) I hit a weird issue where the whole install screen froze when I tried
the following:
a. With the defaults, i.e. Metron Parsers showing error about KAFKA
colocation
b. Added a KAFKA host to the same as Metron Parsers -> Now, the error shows
STORM SUPERVISOR colocation
c. Removed the KAFKA host that was added in Step 'a' above.
d. And the Ambari installer froze, unable to click the "Next" button.
---
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.
---
