[
https://issues.apache.org/jira/browse/YETUS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223860#comment-16223860
]
Sean Busbey commented on YETUS-570:
-----------------------------------
HBase has some machine metrics we grab before our Yetus runs start to try to
get a handle on our test stability. Many of them only really need a snapshot
(what's the CPU config, how many disks are there), but some would benefit from
sampling ala the thread count one in your wip patch.
* memory use
* disk io
* disk free space
I'd like to add them. Should I wait until this patch lands, or would posting a
wip now based on your patch be useful?
> Report and optionally kill stale JVMs between unit test modules
> ---------------------------------------------------------------
>
> Key: YETUS-570
> URL: https://issues.apache.org/jira/browse/YETUS-570
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Affects Versions: 0.6.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: YETUS-570.wip.00.patch, YETUS-570.wip.01.patch
>
>
> YETUS-561 does a great job of preventing fork bombs and stale processes from
> destroying machines. However, Yetus should do a better job of:
> a) Reporting when that happens
> b) Preventing that from happening
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
