hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8272) Erasure Coding: simplify the retry logic in DFSStripedInputStream
Date Tue, 28 Apr 2015 22:51:06 GMT

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

Jing Zhao updated HDFS-8272:
    Attachment: h8272-HDFS-7285.001.patch

Thanks again for the review, Zhe! Update the patch to address your comments (including DFSInputStream
changes). The main change is to only refetch the key/token once for the group.

About the encryption key retry logic, I think it is handled while creating the block reader.
More specifically, while creating the TCP peer in {{BlockReaderFactory#getRemoteBlockReaderFromTcp}},
the sasl protocol is triggered during which the encryptionKey can be refetched.

> Erasure Coding: simplify the retry logic in DFSStripedInputStream
> -----------------------------------------------------------------
>                 Key: HDFS-8272
>                 URL: https://issues.apache.org/jira/browse/HDFS-8272
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: h8272-HDFS-7285.000.patch, h8272-HDFS-7285.001.patch
> Currently in DFSStripedInputStream the retry logic is still the same with DFSInputStream.
More specifically, every failed read will try to search for another source node. And an exception
is thrown when no new source node can be identified. This logic is not appropriate for EC
inputstream and can be simplified.

This message was sent by Atlassian JIRA

View raw message