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

Hudson commented on HADOOP-9894:
--------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1533 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1533/])
HADOOP-9894.  Race condition in Shell leads to logged error stream handling 
exceptions (Arpit Agarwal) (arp: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1518420)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java

                
> Race condition in Shell leads to logged error stream handling exceptions
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-9894
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9894
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.1.0-beta
>            Reporter: Jason Lowe
>            Assignee: Arpit Agarwal
>         Attachments: hadoop-9894.01.patch
>
>
> Shell.runCommand starts an error stream handling thread and normally joins 
> with it before closing the error stream.  However if parseExecResult throws 
> an exception (e.g.: like Stat.parseExecResult does for FileNotFoundException) 
> then the error thread is not joined and the error stream can be closed before 
> the error stream handling thread is finished.  This causes the error stream 
> handling thread to log an exception backtrace for a "normal" situation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to