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

Allen Wittenauer commented on HDFS-12711:
-----------------------------------------

Thanks!

I'll have to play around with sending a SIGQUIT. The other thing is that some 
process types may need different types of signals.  It might be useful to be 
able to define the "signal path"... e.g., surefire processes get QUIT -> TERM 
-> KILL.

I know the other thing is for archiver to save off the stack trace logs  
(hs_err_pidXXXXXX.log files) we do get.  That's just a settings thing that I've 
been too busy to setup in Jenkins. 

For now, though, I'm sort of tired at looking at this problem and will go work 
on something else for a while.  It's at the point that the issues are firmly 
contained from ASF build infra perspective and rests solely in the hands of the 
Hadoop community to fix their unit tests (or even base code) to be less broken. 
 

> deadly hdfs test
> ----------------
>
>                 Key: HDFS-12711
>                 URL: https://issues.apache.org/jira/browse/HDFS-12711
>             Project: Hadoop HDFS
>          Issue Type: Test
>    Affects Versions: 2.9.0, 2.8.2
>            Reporter: Allen Wittenauer
>            Priority: Critical
>         Attachments: HDFS-12711.branch-2.00.patch, fakepatch.branch-2.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to