[
https://issues.apache.org/jira/browse/SLIDER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095793#comment-14095793
]
ASF subversion and git services commented on SLIDER-202:
--------------------------------------------------------
Commit 52bd11b5d4d3a17f231e5343c0bfa6c39492fbb3 in incubator-slider's branch
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=52bd11b ]
SLIDER-202 monkey has mock tests and is set to run in AM if enabled
> add integral/configurable chaos monkey to slider AM
> ----------------------------------------------------
>
> Key: SLIDER-202
> URL: https://issues.apache.org/jira/browse/SLIDER-202
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster, test
> Affects Versions: Slider 0.40
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The slider funtests trigger container and AM failure in the test code via RPC
> calls "killContainer" and "amSuicide". This is good for standalone tests, but
> complicates functional test deployments where we can't easily run such logic
> client-side.
> Proposed: a built in chaos monkey service in the AM which, when enabled, will
> -at given intervals- check to see if a container or AM restart should be
> triggered based on some preconfigured probabilities.
> This will be embedded and can be used in production if desired.
> e.g, short test:
> {code}
> interval = 60s, P(AM)=0.1, P(Container)=1.0
> {code}
> long test
> {code}
> interval = 600s, P(AM)=0.01, P(Container)=0.5
> {code}
> production
> {code}
> interval = 24h, P(AM)=0., P(Container)=0.1
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
