[
https://issues.apache.org/jira/browse/BIGTOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310923#comment-14310923
]
Konstantin Boudnik commented on BIGTOP-1521:
--------------------------------------------
As an action plan I'd pick a small cluster - say 3 nodes, ran all the Hadoop
tests we have and timed them. Then set the timeout at say 300% level on them.
Something along these lines should be enough, no?
> Bigtop smoke-tests hierarchy and fast failure
> ---------------------------------------------
>
> Key: BIGTOP-1521
> URL: https://issues.apache.org/jira/browse/BIGTOP-1521
> Project: Bigtop
> Issue Type: Bug
> Components: tests
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Assignee: Dasha Boudnik
> Fix For: 0.9.0
>
>
> *Problem* Sometimes YARN jobs can hang indefinetly, and in the case of the
> {{smoke-tests}} , we also can get an infinite hang it appears.
> This can be reproduced by simply messing up/deleting the core hadoop
> components from {{bigtop-deploy/vm/vagrant-puppet}}'s provision script puppet
> conf file {{provision.sh}} and running {{vagrant up}}.
> *Solution* Let add some smarts to the smoke tester - such that the basic yarn
> services (i. think hadoop-smoke in test-artifcacts does this maybe ) are
> confirmed before any yarn based tests are ran.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
