[
https://issues.apache.org/jira/browse/BIGTOP-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916655#comment-13916655
]
Konstantin Boudnik commented on BIGTOP-1198:
--------------------------------------------
Where I struggle with this approach right now is to see how stressing out the
hardware can help to test a JVM's managed application. In a sense, I am not
convinced that limiting CPU resources or RAM available for allocation via
external means can help to expose internal issues with say namenode. If someone
sees it differently - please correct me!
Also, this isn't a smoke test by a long stretch - it could be some sort of
special case load testing. And there might be some value in it.
Oh, and btw - avoid using {{println}} calls - use logger calls instead.
> itest should provide smoke tests with a way to simulate heavy load on the node
> ------------------------------------------------------------------------------
>
> Key: BIGTOP-1198
> URL: https://issues.apache.org/jira/browse/BIGTOP-1198
> Project: Bigtop
> Issue Type: New Feature
> Components: Tests
> Affects Versions: 0.7.0
> Reporter: Mikhail Antonov
> Assignee: Mikhail Antonov
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1198.patch
>
>
> See BIGTOP-1192 for general description of failures injection framework for
> smoke tests.
> item should have failure type which can create simulated high
> CPU/memory/network/IO utilization on the particular host in cluster.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
