hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
Date Thu, 03 Sep 2015 23:15:45 GMT

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

Mingliang Liu updated HDFS-9012:
    Attachment: HDFS-9012.002.patch

Thank you [~wheat9] for your insight. Pre-parsing the OOB timeout config value and saving
them will definitely make it better.

The v2 patch moves the OOB timeouts related code to {{DataNode}} class.

> Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
> ------------------------------------------------------------------------------------
>                 Key: HDFS-9012
>                 URL: https://issues.apache.org/jira/browse/HDFS-9012
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>         Attachments: HDFS-9012.000.patch, HDFS-9012.001.patch, HDFS-9012.002.patch
> The {{package org.apache.hadoop.hdfs.protocol.datatransfer.PipelineAck}} class is used
in client module classes (e.g. {{DataStreamer$ResponseProcessor}} in {{DFSInputStream}} and
{{DFSOutputStream}}). This jira tracks the effort of moving this class to {{hadoop-hdfs-client}}
> We should keep the static attribute {{OOB_TIMEOUT}} and helper method {{getOOBTimeout}}
in the {{hadoop-hdfs}} module as they're not used (by now) in {{hadoop-hdfs-client}} module.
Meanwhile, we don't create the {{HdfsConfiguration}} statically if we can pass the correct
{{conf}} object.
> The checkstyle warnings can be addressed in [HDFS-8979|https://issues.apache.org/jira/browse/HDFS-8979].

This message was sent by Atlassian JIRA

View raw message