[
https://issues.apache.org/jira/browse/YETUS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-570:
-----------------------------------
Attachment: YETUS-570.04.patch
-04:
* rebase
* fix Sean's feedback (thanks!)
* add more timeout to pid_kill
* fix --reaperdockeronly to actually work
* add a sleep before the reap to let things settle down
I still haven't been able to get a complete build of hadoop's branch-2, but:
* I've gotten MUCH farther
* The changes in this version of the patch reflect new experience from that;
the killing was way too aggressive based upon the log showing processes
disappearing. (That chunk of code might need more tuning later, but for now
this should be Good Enough(tm)).
* all attempts past few days have been due to other things, from what I can
see. :)
I'll be kicking off another run here in a bit.
> 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
> Priority: Major
> Attachments: YETUS-570.03.patch, YETUS-570.04.patch,
> YETUS-570.wip.00.patch, YETUS-570.wip.01.patch, YETUS-570.wip.02.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)
