You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Yi Liu (JIRA)" <ji...@apache.org> on 2015/09/20 02:05:04 UTC

[jira] [Commented] (HDFS-9113) ErasureCodingWorker#processErasureCodingTasks should not fail to process remaining tasks due to one invalid ECTask

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

Yi Liu commented on HDFS-9113:
------------------------------

+1, thanks Uma.
I think this is caused by HDFS-8899 where change to use a threadpool but mistake to remove original {{try... catch..}}

> ErasureCodingWorker#processErasureCodingTasks should not fail to process remaining tasks due to one invalid ECTask
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-9113
>                 URL: https://issues.apache.org/jira/browse/HDFS-9113
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode
>    Affects Versions: HDFS-7285
>            Reporter: Uma Maheswara Rao G
>            Assignee: Uma Maheswara Rao G
>            Priority: Minor
>         Attachments: HDFS-9113-HDFS-7285-00.patch
>
>
> Currently processErasureCodingTasks method submits ecTasks to thread pool service for processing the tasks. While submitting we initialize ReconstructAndTransferBlock with each ecTask and submit it. There are chances ReconstructAndTransferBlock initialization can fail due to wrong values as we had preconditions for parameter validations in Ctor. Anyway, whatever may be the case, processErasureCodingTasks should not fail and throw exceptions out as it could prevent processing other tasks in the list. 



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