[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

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

[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042802#comment-17042802 ] Ayush Saxena commented on HDFS-15041: - Thanx [~zhuqi] for the update. v004 LGTM +1 (Pending Jenkins)

[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042798#comment-17042798 ] zhuqi commented on HDFS-15041: -- cc [~ayushtkn] Thanks for your review. I have fixed it. > Make

[jira] [Updated] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15041: - Attachment: HDFS-15041.004.patch Status: Patch Available (was: In Progress) > Make MAX_LOCK_HOLD_MS and

[jira] [Updated] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15041: - Status: In Progress (was: Patch Available) > Make MAX_LOCK_HOLD_MS and full queue size configurable >

[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042795#comment-17042795 ] Ayush Saxena commented on HDFS-15041: - Thanx [~zhuqi] for update. {code:java} +

[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042783#comment-17042783 ] zhuqi commented on HDFS-15041: -- cc [~ayushtkn]    [~weichiu] I have changed the configuration to support

[jira] [Updated] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15041: - Attachment: HDFS-15041.003.patch Status: Patch Available (was: In Progress) > Make MAX_LOCK_HOLD_MS and

[jira] [Updated] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuqi updated HDFS-15041: - Status: In Progress (was: Patch Available) > Make MAX_LOCK_HOLD_MS and full queue size configurable >

[jira] [Comment Edited] (HDFS-15186) Erasure Coding: Decommission may generate the parity block's content with all 0 in some case

[ https://issues.apache.org/jira/browse/HDFS-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042780#comment-17042780 ] Fei Hui edited comment on HDFS-15186 at 2/23/20 2:52 AM: - [~yaoguangdong]Thanks

[jira] [Commented] (HDFS-15186) Erasure Coding: Decommission may generate the parity block's content with all 0 in some case

[ https://issues.apache.org/jira/browse/HDFS-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042780#comment-17042780 ] Fei Hui commented on HDFS-15186: [~yaoguangdong]Thanks for reporting this !Good Catch! Sorry for late, I

[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full queue size configurable

[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042703#comment-17042703 ] Ayush Saxena commented on HDFS-15041: - Thanx [~zhuqi]  for the patch. we can make the configuration

[jira] [Commented] (HDFS-15103) JMX endpoint and "dfsadmin" report 1 corrupt block; "fsck" reports 0

[ https://issues.apache.org/jira/browse/HDFS-15103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042702#comment-17042702 ] Ayush Saxena commented on HDFS-15103: - The corrupt replica can be from a open file, the fsck has

[jira] [Commented] (HDFS-15114) JournalNodes' committed-txid file includes aborted transaction, breaks NameNode startup

[ https://issues.apache.org/jira/browse/HDFS-15114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042696#comment-17042696 ] Ayush Saxena commented on HDFS-15114: - Thanx [~Steven Rand]  for the report. Are you able to

[jira] [Commented] (HDFS-15124) Crashing bugs in NameNode when using a valid configuration for `dfs.namenode.audit.loggers`

[ https://issues.apache.org/jira/browse/HDFS-15124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042695#comment-17042695 ] Ayush Saxena commented on HDFS-15124: - Thanx Everyone for the work here. [~ctest.team] you can check

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

[ https://issues.apache.org/jira/browse/HDFS-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042631#comment-17042631 ] Ayush Saxena commented on HDFS-15176: - Thanx [~LiJinglun] for the patch. nit : In the doc, can you

[jira] [Commented] (HDFS-15182) TestBlockManager#testOneOfTwoRacksDecommissioned() fail in trunk

[ https://issues.apache.org/jira/browse/HDFS-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042474#comment-17042474 ] Hudson commented on HDFS-15182: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17978 (See

[jira] [Commented] (HDFS-15186) Erasure Coding: Decommission may generate the parity block's content with all 0 in some case

[ https://issues.apache.org/jira/browse/HDFS-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042472#comment-17042472 ] Yao Guangdong commented on HDFS-15186: -- [~ayushtkn], Yes, you are right. The major reason of the

[jira] [Updated] (HDFS-15182) TestBlockManager#testOneOfTwoRacksDecommissioned() fail in trunk

[ https://issues.apache.org/jira/browse/HDFS-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15182: Fix Version/s: 3.3.0 Hadoop Flags: Reviewed Resolution: Fixed Status:

[jira] [Commented] (HDFS-15182) TestBlockManager#testOneOfTwoRacksDecommissioned() fail in trunk

[ https://issues.apache.org/jira/browse/HDFS-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042465#comment-17042465 ] Ayush Saxena commented on HDFS-15182: - Committed to trunk. Thanx [~leosun08] for the contribution!!!

[jira] [Commented] (HDFS-15186) Erasure Coding: Decommission may generate the parity block's content with all 0 in some case

[ https://issues.apache.org/jira/browse/HDFS-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042458#comment-17042458 ] Ayush Saxena commented on HDFS-15186: - HDFS-14768 tend to make a busy live DN to be considered for