[jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
[ https://issues.apache.org/jira/browse/HDFS-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingliang Liu updated HDFS-9012: Status: Patch Available (was: Open) > 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 > > > 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}} module. > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
[ 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.000.patch > 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 > > > 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}} module. > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
[ 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.001.patch The v1 patch rebases from {{trunk}} branch so it will trigger Jenkins again. I think the failing tests may be unrelated. > 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 > > > 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}} module. > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
[ https://issues.apache.org/jira/browse/HDFS-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingliang Liu updated HDFS-9012: Description: 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}} module. 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]. was: 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}} module. 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. > 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 > > > 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}} module. > 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 (v6.3.4#6332)
[jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
[ 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}} module. > 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 (v6.3.4#6332)
[jira] [Updated] (HDFS-9012) Move o.a.h.hdfs.protocol.datatransfer.PipelineAck class to hadoop-hdfs-client module
[ https://issues.apache.org/jira/browse/HDFS-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai updated HDFS-9012: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0 Status: Resolved (was: Patch Available) I've committed the patch to trunk and branch-2. Thanks [~liuml07] for the contribution. > 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 > Fix For: 2.8.0 > > 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}} module. > 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 (v6.3.4#6332)