[
https://issues.apache.org/jira/browse/METRON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531301#comment-15531301
]
ASF GitHub Bot commented on METRON-466:
---------------------------------------
Github user james-sirota commented on the issue:
https://github.com/apache/incubator-metron/pull/279
+1 to this. Here is why. If fulldev can only support 2 running parser
topologies I think it makes sense to let a user pick which 2 they want. The
intention of vagrant dev images is to spin them up to test a PR and then
destroy them. We generally only need a few topologies for that and it is not
the intention to use vagrant images to simulate a full running system. By
having only 2 topologies started by default we will avoid 90% of problems
people have when they spin up the vagrant images and run out of memory. With
that said I will also document what needs to be done to spin up the image with
4 topologies, but put a disclaimer to start at their own risk.
> 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)
