[
https://issues.apache.org/jira/browse/METRON-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531712#comment-15531712
]
Dima Kovalyov commented on METRON-472:
--------------------------------------
vagrant up fails quite frequently indeed most of the time because of the
timeout issues (poor hardware or IO lag).
In my case I just destroy a node and start it again like that:
vagrant node1 destroy
./run.sh
Isn't that how it should be?
Pardon if I completely missing something here.
> Vagrant Quick Dev should have both run.sh and runAgain.sh
> ---------------------------------------------------------
>
> Key: METRON-472
> URL: https://issues.apache.org/jira/browse/METRON-472
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.2.1BETA
> Environment: Vagrant Quick Dev
> Reporter: Otto Fowler
>
> The vagrant quick dev is executed by running run.sh ( as opposed to just
> doing vagrant up in the full dev ). run.sh does the vagrant up, with the
> correct tags declared and the skip solr flag.
> Often the vagrant up does not finish execution, and as recommended you have
> to do a vagrant provision to continue.
> Depending on where in the process you have failed however, you will not
> succeed because you have not declared the same tags and skips.
> There should be another script to be run in the provision/retry case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
