hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14420) Zombie Stomping Session
Date Fri, 16 Oct 2015 16:13:05 GMT

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

stack commented on HBASE-14420:
-------------------------------

FYI [~dimaspivak] ... You are trying to follow along... see above where my reporting is failing...
The issue is that we run the zombie detection even when the build is killed and we 'find'
zombies though its just stuff that was running at kill-time.  Just FYI. I'll try and fix zombie
detector...

> Zombie Stomping Session
> -----------------------
>
>                 Key: HBASE-14420
>                 URL: https://issues.apache.org/jira/browse/HBASE-14420
>             Project: HBase
>          Issue Type: Umbrella
>          Components: test
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>         Attachments: hangers.txt, none_fix (1).txt, none_fix.txt, none_fix.txt, none_fix.txt,
none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt,
none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt, none_fix.txt
>
>
> Patch build are now failing most of the time because we are dropping zombies. I confirm
we are doing this on non-apache build boxes too.
> Left-over zombies consume resources on build boxes (OOME cannot create native threads).
Having to do multiple test runs in the hope that we can get a non-zombie-making build or making
(arbitrary) rulings that the zombies are 'not related' is a productivity sink. And so on...
> This is an umbrella issue for a zombie stomping session that started earlier this week.
Will hang sub-issues of this one. Am running builds back-to-back on little cluster to turn
out the monsters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message