[jira] [Reopened] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiping Zhang reopened HDFS-16570: - > RBF: The router using MultipleDestinationMountTableResolver remove Multiple > subcluster data

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533186#comment-17533186 ] Yuanbo Liu commented on HDFS-16569: --- Regarding Tectonic, seperating deamon threads from NN and

[jira] [Work logged] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?focusedWorklogId=767502=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767502 ] ASF GitHub Bot logged work on HDFS-16570: - Author: ASF GitHub Bot

[jira] [Work logged] (HDFS-16568) dfsadmin -reconfig option to start/query reconfig on all live datanodes

[ https://issues.apache.org/jira/browse/HDFS-16568?focusedWorklogId=767496=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767496 ] ASF GitHub Bot logged work on HDFS-16568: - Author: ASF GitHub Bot

[jira] [Work logged] (HDFS-16568) dfsadmin -reconfig option to start/query reconfig on all live datanodes

[ https://issues.apache.org/jira/browse/HDFS-16568?focusedWorklogId=767486=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767486 ] ASF GitHub Bot logged work on HDFS-16568: - Author: ASF GitHub Bot

[jira] [Commented] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533169#comment-17533169 ] Xiping Zhang commented on HDFS-16570: - The trash path is resolved by removing the prefix of the trash

[jira] [Resolved] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiping Zhang resolved HDFS-16570. - Resolution: Implemented > RBF: The router using MultipleDestinationMountTableResolver remove

[jira] [Updated] (HDFS-16384) Upgrade Netty to 4.1.72.Final

[ https://issues.apache.org/jira/browse/HDFS-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes updated HDFS-16384: Resolution: Abandoned Status: Resolved (was: Patch Available) > Upgrade Netty to

[jira] [Commented] (HDFS-16384) Upgrade Netty to 4.1.72.Final

[ https://issues.apache.org/jira/browse/HDFS-16384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533105#comment-17533105 ] Tamas Penzes commented on HDFS-16384: - [~weichiu] I'm closing this ticket as it is superceded by

[jira] [Work logged] (HDFS-16384) Upgrade Netty to 4.1.72.Final

[ https://issues.apache.org/jira/browse/HDFS-16384?focusedWorklogId=767440=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767440 ] ASF GitHub Bot logged work on HDFS-16384: - Author: ASF GitHub Bot

[jira] [Work logged] (HDFS-16540) Data locality is lost when DataNode pod restarts in kubernetes

[ https://issues.apache.org/jira/browse/HDFS-16540?focusedWorklogId=767411=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767411 ] ASF GitHub Bot logged work on HDFS-16540: - Author: ASF GitHub Bot

[jira] [Resolved] (HDFS-16520) Improve EC pread: avoid potential reading whole block

[ https://issues.apache.org/jira/browse/HDFS-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HDFS-16520. Resolution: Fixed Merged the PR and cherrypicked into branch-3.3. Thanks! > Improve EC

[jira] [Updated] (HDFS-16520) Improve EC pread: avoid potential reading whole block

[ https://issues.apache.org/jira/browse/HDFS-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-16520: --- Fix Version/s: 3.3.4 > Improve EC pread: avoid potential reading whole block >

[jira] [Commented] (HDFS-16571) ABFS: Two BlobCreated get triggered for writing one ABFS file

[ https://issues.apache.org/jira/browse/HDFS-16571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533005#comment-17533005 ] Bryan Chen commented on HDFS-16571: --- Some more findings: the `fs.create(...)` triggers one BlobCreated

[jira] [Updated] (HDFS-16520) Improve EC pread: avoid potential reading whole block

[ https://issues.apache.org/jira/browse/HDFS-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-16520: --- Component/s: erasure-coding > Improve EC pread: avoid potential reading whole block >

[jira] [Updated] (HDFS-16520) Improve EC pread: avoid potential reading whole block

[ https://issues.apache.org/jira/browse/HDFS-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-16520: --- Fix Version/s: 3.4.0 > Improve EC pread: avoid potential reading whole block >

[jira] [Work logged] (HDFS-16520) Improve EC pread: avoid potential reading whole block

[ https://issues.apache.org/jira/browse/HDFS-16520?focusedWorklogId=767329=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767329 ] ASF GitHub Bot logged work on HDFS-16520: - Author: ASF GitHub Bot

[jira] [Created] (HDFS-16571) ABFS: Two BlobCreated get triggered for writing one ABFS file

Bryan Chen created HDFS-16571: - Summary: ABFS: Two BlobCreated get triggered for writing one ABFS file Key: HDFS-16571 URL: https://issues.apache.org/jira/browse/HDFS-16571 Project: Hadoop HDFS

[jira] [Work logged] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?focusedWorklogId=767165=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767165 ] ASF GitHub Bot logged work on HDFS-16570: - Author: ASF GitHub Bot

[jira] [Comment Edited] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532808#comment-17532808 ] JiangHua Zhu edited comment on HDFS-16565 at 5/6/22 11:46 AM: -- Thanks

[jira] [Commented] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532808#comment-17532808 ] JiangHua Zhu commented on HDFS-16565: - Thanks [~hexiaoqiao] for the comment. This phenomenon occurs

[jira] [Work logged] (HDFS-16568) dfsadmin -reconfig option to start/query reconfig on all live datanodes

[ https://issues.apache.org/jira/browse/HDFS-16568?focusedWorklogId=767147=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767147 ] ASF GitHub Bot logged work on HDFS-16568: - Author: ASF GitHub Bot

[jira] [Work logged] (HDFS-16568) dfsadmin -reconfig option to start/query reconfig on all live datanodes

[ https://issues.apache.org/jira/browse/HDFS-16568?focusedWorklogId=767146=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767146 ] ASF GitHub Bot logged work on HDFS-16568: - Author: ASF GitHub Bot

[jira] [Comment Edited] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532790#comment-17532790 ] Xiaoqiao He edited comment on HDFS-16569 at 5/6/22 11:22 AM: - Thanks

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532790#comment-17532790 ] Xiaoqiao He commented on HDFS-16569: Thanks [~yuanbo] for your detailed explanation. It is an

[jira] [Work logged] (HDFS-14750) RBF: Improved isolation for downstream name nodes. {Dynamic}

[ https://issues.apache.org/jira/browse/HDFS-14750?focusedWorklogId=767136=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767136 ] ASF GitHub Bot logged work on HDFS-14750: - Author: ASF GitHub Bot

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532772#comment-17532772 ] Yuanbo Liu commented on HDFS-16569: --- [~ayushtkn] Thanks for your comments. > You mean to say, since the

[jira] [Commented] (HDFS-13243) Get CorruptBlock because of calling close and sync in same time

[ https://issues.apache.org/jira/browse/HDFS-13243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532770#comment-17532770 ] daimin commented on HDFS-13243: --- [~gzh1992n][~weichiu] We have encountered the same problem in our cluster

[jira] [Assigned] (HDFS-13243) Get CorruptBlock because of calling close and sync in same time

[ https://issues.apache.org/jira/browse/HDFS-13243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] daimin reassigned HDFS-13243: - Assignee: daimin (was: Zephyr Guo) > Get CorruptBlock because of calling close and sync in same time >

[jira] [Updated] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiping Zhang updated HDFS-16570: Description: Please look at the following example : hadoop>{color:#FF}hdfs dfsrouteradmin

[jira] [Updated] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDFS-16570: -- Labels: pull-request-available (was: ) > RBF: The router using

[jira] [Work logged] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

[ https://issues.apache.org/jira/browse/HDFS-16570?focusedWorklogId=767133=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767133 ] ASF GitHub Bot logged work on HDFS-16570: - Author: ASF GitHub Bot

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532765#comment-17532765 ] Yuanbo Liu commented on HDFS-16569: --- [~hexiaoqiao] Thanks for your comment. The process is here: 1.

[jira] [Created] (HDFS-16570) RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed

Xiping Zhang created HDFS-16570: --- Summary: RBF: The router using MultipleDestinationMountTableResolver remove Multiple subcluster data under the mount point failed Key: HDFS-16570 URL:

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532761#comment-17532761 ] Ayush Saxena commented on HDFS-16569: - The client has location, that is why the block went into the

[jira] [Updated] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu updated HDFS-16565: Issue Type: Bug (was: Improvement) > DataNode holds a large number of CLOSE_WAIT connections that

[jira] [Commented] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532755#comment-17532755 ] Xiaoqiao He commented on HDFS-16565: [~jianghuazhu] Thanks for your report. Is it possible that

[jira] [Work logged] (HDFS-14750) RBF: Improved isolation for downstream name nodes. {Dynamic}

[ https://issues.apache.org/jira/browse/HDFS-14750?focusedWorklogId=767107=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767107 ] ASF GitHub Bot logged work on HDFS-14750: - Author: ASF GitHub Bot

[jira] [Commented] (HDFS-16569) Consider attaching block location info from client when closing a completed file

[ https://issues.apache.org/jira/browse/HDFS-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532747#comment-17532747 ] Xiaoqiao He commented on HDFS-16569: [~yuanbo] Thanks for your report. Do you mean that last block

[jira] [Updated] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu updated HDFS-16565: Description: There is a strange phenomenon here, DataNode holds a large number of connections in

[jira] [Updated] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu updated HDFS-16565: Environment: CentOS Linux release 7.5.1804 (Core) > DataNode holds a large number of CLOSE_WAIT

[jira] [Assigned] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu reassigned HDFS-16565: --- Assignee: (was: JiangHua Zhu) > DataNode holds a large number of CLOSE_WAIT connections

[jira] [Updated] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu updated HDFS-16565: Attachment: screenshot-1.png > DataNode holds a large number of CLOSE_WAIT connections that are

[jira] [Updated] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu updated HDFS-16565: Description: There is a strange phenomenon here, DataNode holds a large number of connections in

[jira] [Updated] (HDFS-16565) DataNode holds a large number of CLOSE_WAIT connections that are not released

[ https://issues.apache.org/jira/browse/HDFS-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiangHua Zhu updated HDFS-16565: Summary: DataNode holds a large number of CLOSE_WAIT connections that are not released (was:

[jira] [Work logged] (HDFS-16568) dfsadmin -reconfig option to start/query reconfig on all live datanodes

[ https://issues.apache.org/jira/browse/HDFS-16568?focusedWorklogId=767026=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767026 ] ASF GitHub Bot logged work on HDFS-16568: - Author: ASF GitHub Bot