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 "Rakesh R (JIRA)" <ji...@apache.org> on 2016/02/18 19:08:18 UTC

[jira] [Updated] (HDFS-9829) Erasure Coding: Improve few exception handling logic of ErasureCodingWorker

     [ https://issues.apache.org/jira/browse/HDFS-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rakesh R updated HDFS-9829:
---------------------------
    Attachment: HDFS-9829-001.patch

> Erasure Coding: Improve few exception handling logic of ErasureCodingWorker
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-9829
>                 URL: https://issues.apache.org/jira/browse/HDFS-9829
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>            Priority: Minor
>         Attachments: HDFS-9829-001.patch
>
>
> # Cancel remaining reads on InterruptedException.
> {code}
> 	} catch (InterruptedException e) {
>           LOG.info("Read data interrupted.", e);
>           break;
>         }
> {code}
> # Shouldn't fail recontruction due to an IOException errors while reporting corrupt blocks.
> {code}
>           } finally {
>             // report corrupted blocks to NN
>             reportCorruptedBlocks(corruptionMap);
>           }
> {code}
> # Also, use {} instead of string concatenation in logger.
> {code}
> LOG.debug("Using striped reads; pool threads=" + num);
> //...
> LOG.warn("Found Checksum error for " + reader.block + " from "
>                 + reader.source + " at " + e.getPos());
> //...
> LOG.debug("Using striped block reconstruction; pool threads=" + num);
> //..
> LOG.warn("Failed to reconstruct striped block: " + blockGroup, e);
> {code}



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