[
https://issues.apache.org/jira/browse/METRON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531155#comment-15531155
]
ASF GitHub Bot commented on METRON-466:
---------------------------------------
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/279
@james-sirota - a couple of ways:
Pre-deploy:
1) Decide which parser/probe pair you wish to trade.
2) Toggle it off by setting install_(probe): false and add it to
ansible-skip-tags in run.sh in place of 'yaf'.
Post-Deploy
1) Decide which parser/probe pair you wish to trade.
2) Kill the parsing topology and stop the associated sensor.
3) Toggle install_yaf to true.
4) Add yaf-parser to services to start.
4) ./run_ansible_role "sensors,enrichment,monit,start"
> 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)
