You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2017/10/27 14:27:00 UTC

[jira] [Commented] (YETUS-570) Report and optionally kill stale JVMs between unit test modules

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

Allen Wittenauer commented on YETUS-570:
----------------------------------------

This is ultimately a modification to the HBase zombie check, but with two extra twists:  

a) Yetus can do it in-between module test runs, so can keep track of growth between sets of unit tests

b) In the Docker scenario, actually kill the extras since Yetus spawned surefirebooters should be the only ones actually present in the process space

> 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
>
> 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)