[ 
https://issues.apache.org/jira/browse/BIGTOP-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121709#comment-14121709
 ] 

Dawson Choong edited comment on BIGTOP-1388 at 9/4/14 6:26 PM:
---------------------------------------------------------------

Currently only written for TestDFSIO.groovy. Will apply to TestSLive and 
MapReduce.

Added FailureVars - a class that manages variables, objects, and command line 
parameters for cluster failures.

Added FailureExecutor - a runnable that is executed by a test such as 
TestDFSIO. This class spawns cluster failure threads that run in parallel to 
the hadoop/mapreduce tests.

(By default, all parameters are off or set to false.)
Features:

    Use -Dhost=name to specify host being tested on
    Use -DremoteHost=name to specify remote host name being tested on.
    Use -DrunAll=true to run all cluster failures
    Use -DserviceRestart=true to perform a cron or crond service restart.
    Use -DserviceKill=true to perform a service kill.
    Use -Dshutdown=true to perform network shutdown and restart.
    Use -Dservice=name to specify which service being used for restart/kill. 
(default is crond)
    Use -DfailureDelay=time to specify time (in seconds) in between each 
failure function.
    Use -DstartDelay=time to specify time (in seconds) before first failure.
    Use -DkillDuration=time to specify the duration (in seconds) a service is 
down for.


was (Author: dawson.choong):
Currently only working for TestDFSIO.groovy. Will apply to TestSLive and 
MapReduce.

Added FailureVars - a class that manages variables, objects, and command line 
parameters for cluster failures.

Added FailureExecutor - a runnable that is executed by a test such as 
TestDFSIO. This class spawns cluster failure threads that run in parallel to 
the hadoop/mapreduce tests.

(By default, all parameters are off or set to false.)
Features:

    Use -Dhost=name to specify host being tested on
    Use -DremoteHost=name to specify remote host name being tested on.
    Use -DrunAll=true to run all cluster failures
    Use -DserviceRestart=true to perform a cron or crond service restart.
    Use -DserviceKill=true to perform a service kill.
    Use -Dshutdown=true to perform network shutdown and restart.
    Use -Dservice=name to specify which service being used for restart/kill. 
(default is crond)
    Use -DfailureDelay=time to specify time (in seconds) in between each 
failure function.
    Use -DstartDelay=time to specify time (in seconds) before first failure.
    Use -DkillDuration=time to specify the duration (in seconds) a service is 
down for.

> Use cluster failure tests during other tests with command line parametrization
> ------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1388
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1388
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: tests
>    Affects Versions: 0.7.0
>            Reporter: Dawson Choong
>              Labels: patch
>             Fix For: 0.8.0
>
>         Attachments: BIGTOP-1388.patch
>
>
> User can run tests from ClusterFailureTests.groovy simultaneously with 
> another test, such as mapr and longevity, in order to check test completion 
> during node failures. The cluster failure tests should be able to be 
> specified as a command line parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to