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

Hudson commented on MAPREDUCE-5194:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1462 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1462/])
    MAPREDUCE-5194. Heed interrupts during Fetcher shutdown. (Revision 1494416)

     Result = FAILURE
cdouglas : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1494416
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/Fetcher.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/OnDiskMapOutput.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/task/reduce/TestFetcher.java

                
> Heed interrupts during Fetcher shutdown
> ---------------------------------------
>
>                 Key: MAPREDUCE-5194
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5194
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: task
>            Reporter: Chris Douglas
>            Assignee: Chris Douglas
>            Priority: Minor
>             Fix For: 2.1.0-beta
>
>         Attachments: M5194-1.patch, M5194-2.patch, M5194.patch
>
>
> In the current implementation, {{Fetcher}} instances usually exit gracefully 
> when the shuffle succeeds. When it fails, threads are interrupted, but may 
> continue running harmlessly until the JVM shuts down.
> However, to generate consistent checkpoints, these threads should exit 
> cleanly to quiesce the state of the shuffle.

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