[
https://issues.apache.org/jira/browse/METRON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531226#comment-15531226
]
ASF GitHub Bot commented on METRON-466:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/279
Ok, just to clarify a bit; I think what is happening is that the yaf
topology (which does exist) does not run by default (this was changed a while
back because of resource constraints), but that does not prevent it from
installing the yaf probe that pushes data to kafka. It's the yaf probe that
@dlyle65535 is stopping by not installing it.
In general, just my $0.02, but I tend think the proper behavior is as
follows:
* All sensors get installed by default; bro, snort, yaf, etc.
* None of them get started by default in either full-dev or quick-dev. If
you want them to start, turn them on via monit
I'm not sure this should be within the scope of this PR, which is why
@dlyle65535 made METRON-467. As for what we do in the interrim, I'd say that
either:
* we either are ok with not installing yaf
* we make the sensors in the `services_to_start` not start, not just the
topologies.
Thoughts and corrections would be greatly appreciated. :)
> Full Dev Platform build sometimes fails
> ---------------------------------------
>
> Key: METRON-466
> URL: https://issues.apache.org/jira/browse/METRON-466
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Assignee: David M. Lyle
>
> Full Dev Platform build will sometimes fail with:
> "Ambari client exception occurred: No JSON object could be decoded"
> As a workaround to the services not all starting, we have 2 calls to start
> all services in the Vagrant deploy. The second call seems to fail if the
> services are already started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
