[jira] [Commented] (HDFS-15176) Enable GcTimePercentage Metric in NameNode's JvmMetrics.

2020-02-17 Thread Hadoop QA (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038845#comment-17038845 ] Hadoop QA commented on HDFS-15176: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-15177) Split datanode invalide block deletion, to avoid the FsDatasetImpl lock too much time.

2020-02-17 Thread zhuqi (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15177: - Summary: Split datanode invalide block deletion, to avoid the FsDatasetImpl lock too much time. (was: Split

[jira] [Updated] (HDFS-15177) Split datanode invalide block deletion, to avoid the FsDatasetImpl lock too many time.

2020-02-17 Thread zhuqi (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15177: - Description: In our cluster, the datanode receive the delete command with too many blocks deletion when we have

[jira] [Created] (HDFS-15178) Federation: Add missing FederationClientInterceptor APIs

2020-02-17 Thread D M Murali Krishna Reddy (Jira)
D M Murali Krishna Reddy created HDFS-15178: --- Summary: Federation: Add missing FederationClientInterceptor APIs Key: HDFS-15178 URL: https://issues.apache.org/jira/browse/HDFS-15178 Project:

[jira] [Updated] (HDFS-15177) Split datanode invalide block deletion, to avoid the FsDatasetImpl lock too many time.

2020-02-17 Thread zhuqi (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15177: - Description: In our cluster, the datanode receive the delete command with too many blocks deletion when we have

[jira] [Created] (HDFS-15177) Split datanode invalide block deletion, to avoid the FsDatasetImpl lock too many time.

2020-02-17 Thread zhuqi (Jira)
zhuqi created HDFS-15177: Summary: Split datanode invalide block deletion, to avoid the FsDatasetImpl lock too many time. Key: HDFS-15177 URL: https://issues.apache.org/jira/browse/HDFS-15177 Project: Hadoop

[jira] [Commented] (HDFS-15120) Refresh BlockPlacementPolicy at runtime.

2020-02-17 Thread Hadoop QA (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038793#comment-17038793 ] Hadoop QA commented on HDFS-15120: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Updated] (HDFS-15176) Enable GcTimePercentage Metric in NameNode's JvmMetrics.

2020-02-17 Thread Jinglun (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinglun updated HDFS-15176: --- Attachment: HDFS-15176.001.patch Status: Patch Available (was: Open) > Enable GcTimePercentage

[jira] [Created] (HDFS-15176) Enable GcTimePercentage Metric in NameNode's JvmMetrics.

2020-02-17 Thread Jinglun (Jira)
Jinglun created HDFS-15176: -- Summary: Enable GcTimePercentage Metric in NameNode's JvmMetrics. Key: HDFS-15176 URL: https://issues.apache.org/jira/browse/HDFS-15176 Project: Hadoop HDFS Issue Type:

[jira] [Updated] (HDFS-15120) Refresh BlockPlacementPolicy at runtime.

2020-02-17 Thread Jinglun (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinglun updated HDFS-15120: --- Attachment: HDFS-15120.003.patch > Refresh BlockPlacementPolicy at runtime. >

[jira] [Commented] (HDFS-15172) Remove unnecessary deadNodeDetectInterval in DeadNodeDetector#checkDeadNodes()

2020-02-17 Thread Lisheng Sun (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038721#comment-17038721 ] Lisheng Sun commented on HDFS-15172: Thank [~elgoiri] for review. This jira solves the problem that

[jira] [Commented] (HDFS-15149) TestDeadNodeDetection test cases time-out

2020-02-17 Thread Ahmed Hussein (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038673#comment-17038673 ] Ahmed Hussein commented on HDFS-15149: -- The poll period and waiting time (5000 and 10) in

[jira] [Commented] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Hadoop QA (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038665#comment-17038665 ] Hadoop QA commented on HDFS-15167: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-12459) Fix revert: Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

2020-02-17 Thread Kihwal Lee (Jira)
[ https://issues.apache.org/jira/browse/HDFS-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038658#comment-17038658 ] Kihwal Lee commented on HDFS-12459: --- We discovered HDFS-11156 was still in branch-2.10. Unreverted, it

[jira] [Updated] (HDFS-12459) Fix revert: Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

2020-02-17 Thread Kihwal Lee (Jira)
[ https://issues.apache.org/jira/browse/HDFS-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-12459: -- Fix Version/s: 2.10.1 3.1.4 > Fix revert: Add new op GETFILEBLOCKLOCATIONS to

[jira] [Commented] (HDFS-11156) Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

2020-02-17 Thread Kihwal Lee (Jira)
[ https://issues.apache.org/jira/browse/HDFS-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038653#comment-17038653 ] Kihwal Lee commented on HDFS-11156: --- Reverted from only 2.10 for now. I also cherry-picked HDFS-12459.

[jira] [Commented] (HDFS-11156) Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

2020-02-17 Thread Kihwal Lee (Jira)
[ https://issues.apache.org/jira/browse/HDFS-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038590#comment-17038590 ] Kihwal Lee commented on HDFS-11156: --- Contrary to the Fix Version (3.0.0-alpha2) of this jira, the

[jira] [Commented] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Ayush Saxena (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038573#comment-17038573 ] Ayush Saxena commented on HDFS-15167: - Handled in v8 > Block Report Interval shouldn't be reset

[jira] [Updated] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Ayush Saxena (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15167: Attachment: HDFS-15167-08.patch > Block Report Interval shouldn't be reset apart from first Block

[jira] [Commented] (HDFS-15172) Remove unnecessary deadNodeDetectInterval in DeadNodeDetector#checkDeadNodes()

2020-02-17 Thread Jira
[ https://issues.apache.org/jira/browse/HDFS-15172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038568#comment-17038568 ] Íñigo Goiri commented on HDFS-15172: It looks like you are doing part of this in HDFS-15149 too. What

[jira] [Commented] (HDFS-15149) TestDeadNodeDetection test cases time-out

2020-02-17 Thread Jira
[ https://issues.apache.org/jira/browse/HDFS-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038565#comment-17038565 ] Íñigo Goiri commented on HDFS-15149: The part about manually enabling/disabling the thread is not the

[jira] [Commented] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Jira
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038562#comment-17038562 ] Íñigo Goiri commented on HDFS-15167: This looks good, just a minor comment. In the javadoc, where we

[jira] [Commented] (HDFS-15149) TestDeadNodeDetection test cases time-out

2020-02-17 Thread Hadoop QA (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038552#comment-17038552 ] Hadoop QA commented on HDFS-15149: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Hadoop QA (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038510#comment-17038510 ] Hadoop QA commented on HDFS-15167: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-15104) If block is not reported by any Datanode, the flag corrupt of BlockLocation should be marked as true.

2020-02-17 Thread Yang Yun (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038421#comment-17038421 ] Yang Yun commented on HDFS-15104: - For the block, it's missing. But for the file, it's corrupt as fsck

[jira] [Updated] (HDFS-15149) TestDeadNodeDetection test cases time-out

2020-02-17 Thread Lisheng Sun (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisheng Sun updated HDFS-15149: --- Attachment: HDFS-15149-001.patch Status: Patch Available (was: Open) >

[jira] [Commented] (HDFS-15104) If block is not reported by any Datanode, the flag corrupt of BlockLocation should be marked as true.

2020-02-17 Thread Ayush Saxena (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038373#comment-17038373 ] Ayush Saxena commented on HDFS-15104: - How can u say that block is corrupt, if no datanode has

[jira] [Commented] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Ayush Saxena (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038360#comment-17038360 ] Ayush Saxena commented on HDFS-15167: - Thanx [~elgoiri] for the review. Added comments as suggested.

[jira] [Updated] (HDFS-15167) Block Report Interval shouldn't be reset apart from first Block Report

2020-02-17 Thread Ayush Saxena (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15167: Attachment: HDFS-15167-07.patch > Block Report Interval shouldn't be reset apart from first Block

[jira] [Updated] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

2020-02-17 Thread Yicong Cai (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yicong Cai updated HDFS-15175: -- Description:   {panel:title=Crash exception} 2020-02-16 09:24:46,426 [507844305] - ERROR [Edit log

[jira] [Created] (HDFS-15175) Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog

2020-02-17 Thread Yicong Cai (Jira)
Yicong Cai created HDFS-15175: - Summary: Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog Key: HDFS-15175 URL: https://issues.apache.org/jira/browse/HDFS-15175

[jira] [Commented] (HDFS-15173) RBF: Delete repeated configuration 'dfs.federation.router.metrics.enable'

2020-02-17 Thread panlijie (Jira)
[ https://issues.apache.org/jira/browse/HDFS-15173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038177#comment-17038177 ] panlijie commented on HDFS-15173: - Thanks for your review ! [~aajisaka] > RBF: Delete repeated