[jira] [Commented] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032815#comment-17032815 ] Ayush Saxena commented on HDFS-15115: - Thanx [~wzx513] for the patch. The test failur

[jira] [Assigned] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena reassigned HDFS-15115: --- Assignee: wangzhixiang (was: David Mollitor) > Namenode crash caused by NPE in BlockPlaceme

[jira] [Created] (HDFS-15157) Fix compilation failure for branch-3.1

Ayush Saxena created HDFS-15157: --- Summary: Fix compilation failure for branch-3.1 Key: HDFS-15157 URL: https://issues.apache.org/jira/browse/HDFS-15157 Project: Hadoop HDFS Issue Type: Bug

[jira] [Updated] (HDFS-15157) Fix compilation failure for branch-3.1

[ https://issues.apache.org/jira/browse/HDFS-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15157: Status: Patch Available (was: Open) > Fix compilation failure for branch-3.1 > ---

[jira] [Updated] (HDFS-15157) Fix compilation failure for branch-3.1

[ https://issues.apache.org/jira/browse/HDFS-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15157: Attachment: HDFS-15157-branch-3.1-01.patch > Fix compilation failure for branch-3.1 > -

[jira] [Commented] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032822#comment-17032822 ] Ayush Saxena commented on HDFS-15115: - Committed to trunk and branch-3.2 Thanx [~wzx5

[jira] [Updated] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

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

[jira] [Commented] (HDFS-15158) The number of failed volumes mismatch with volumeFailures of Datanode metrics

[ https://issues.apache.org/jira/browse/HDFS-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032853#comment-17032853 ] Ayush Saxena commented on HDFS-15158: - Thanx [~hadoop_yangyun] for the report. Pleas

[jira] [Commented] (HDFS-15157) Fix compilation failure for branch-3.1

[ https://issues.apache.org/jira/browse/HDFS-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032854#comment-17032854 ] Ayush Saxena commented on HDFS-15157: - Test Failures Unrelated > Fix compilation fai

[jira] [Commented] (HDFS-15133) Use rocksdb to store NameNode inode and blockInfo

[ https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033008#comment-17033008 ] Ayush Saxena commented on HDFS-15133: - bq. IMO Storing the INode into RocksDB doesn't

[jira] [Commented] (HDFS-15157) Fix compilation failure for branch-3.1

[ https://issues.apache.org/jira/browse/HDFS-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033107#comment-17033107 ] Ayush Saxena commented on HDFS-15157: - Committed to branch-3.1 Thanx [~elgoiri] for t

[jira] [Updated] (HDFS-15157) Fix compilation failure for branch-3.1

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

[jira] [Commented] (HDFS-15133) Use rocksdb to store NameNode inode and blockInfo

[ https://issues.apache.org/jira/browse/HDFS-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033184#comment-17033184 ] Ayush Saxena commented on HDFS-15133: - I had a quick try on this. [~maobaolong] first

[jira] [Commented] (HDFS-15158) The number of failed volumes mismatch with volumeFailures of Datanode metrics

[ https://issues.apache.org/jira/browse/HDFS-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033202#comment-17033202 ] Ayush Saxena commented on HDFS-15158: - Thanx [~hadoop_yangyun] for the update. Minor

[jira] [Commented] (HDFS-15158) The number of failed volumes mismatch with volumeFailures of Datanode metrics

[ https://issues.apache.org/jira/browse/HDFS-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033268#comment-17033268 ] Ayush Saxena commented on HDFS-15158: - The latest patch LGTM +1 > The number of fail

[jira] [Commented] (HDFS-15158) The number of failed volumes mismatch with volumeFailures of Datanode metrics

[ https://issues.apache.org/jira/browse/HDFS-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033271#comment-17033271 ] Ayush Saxena commented on HDFS-15158: - Committed to trunk. Thanx [~hadoop_yangyun] fo

[jira] [Updated] (HDFS-15158) The number of failed volumes mismatch with volumeFailures of Datanode metrics

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

[jira] [Commented] (HDFS-15154) Allow only hdfs superusers the ability to assign HDFS storage policies

[ https://issues.apache.org/jira/browse/HDFS-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033392#comment-17033392 ] Ayush Saxena commented on HDFS-15154: - In simple terms if ADMINISTRATORS is configure

[jira] [Commented] (HDFS-14854) Create improved decommission monitor implementation

[ https://issues.apache.org/jira/browse/HDFS-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033397#comment-17033397 ] Ayush Saxena commented on HDFS-14854: - hi [~sodonnell] for the work here. Do you hav

[jira] [Comment Edited] (HDFS-14854) Create improved decommission monitor implementation

[ https://issues.apache.org/jira/browse/HDFS-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033397#comment-17033397 ] Ayush Saxena edited comment on HDFS-14854 at 2/10/20 10:58 AM:

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034237#comment-17034237 ] Ayush Saxena commented on HDFS-15161: - Seems the title of both JIRA's are same, what

[jira] [Created] (HDFS-15162) Optimize frequency of regular block reports

Ayush Saxena created HDFS-15162: --- Summary: Optimize frequency of regular block reports Key: HDFS-15162 URL: https://issues.apache.org/jira/browse/HDFS-15162 Project: Hadoop HDFS Issue Type: Imp

[jira] [Commented] (HDFS-15086) Block scheduled counter never get decremet if the block got deleted before replication.

[ https://issues.apache.org/jira/browse/HDFS-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035025#comment-17035025 ] Ayush Saxena commented on HDFS-15086: - There was a discussion about it in some Jira c

[jira] [Commented] (HDFS-15127) RBF: Do not allow writes when a subcluster is unavailable for HASH_ALL mount points.

[ https://issues.apache.org/jira/browse/HDFS-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035393#comment-17035393 ] Ayush Saxena commented on HDFS-15127: - Committed to trunk. Thanx [~elgoiri] for the

[jira] [Updated] (HDFS-15127) RBF: Do not allow writes when a subcluster is unavailable for HASH_ALL mount points.

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

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035408#comment-17035408 ] Ayush Saxena commented on HDFS-15161: - v002 LGTM +1 > When evictableMmapped or evict

[jira] [Commented] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035434#comment-17035434 ] Ayush Saxena commented on HDFS-15161: - Committed to trunk to branch-2.9 Thanx [~leos

[jira] [Updated] (HDFS-15161) When evictableMmapped or evictable size is zero, do not throw NoSuchElementException in ShortCircuitCache#close()

[ https://issues.apache.org/jira/browse/HDFS-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15161: Fix Version/s: 2.10.1 3.2.2 3.1.4 2.9.3

[jira] [Created] (HDFS-15164) Fix TestDelegationTokensWithHA

Ayush Saxena created HDFS-15164: --- Summary: Fix TestDelegationTokensWithHA Key: HDFS-15164 URL: https://issues.apache.org/jira/browse/HDFS-15164 Project: Hadoop HDFS Issue Type: Bug

[jira] [Commented] (HDFS-15118) [SBN Read] Slow clients when Observer reads are enabled but there are no Observers on the cluster.

[ https://issues.apache.org/jira/browse/HDFS-15118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035507#comment-17035507 ] Ayush Saxena commented on HDFS-15118: - Seems TestDelegationTokensWithHA was related.

[jira] [Updated] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15164: Attachment: HDFS-15164-01.patch > Fix TestDelegationTokensWithHA > -- >

[jira] [Updated] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15164: Status: Patch Available (was: Open) > Fix TestDelegationTokensWithHA > ---

[jira] [Commented] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035508#comment-17035508 ] Ayush Saxena commented on HDFS-15164: - Suspect HDFS-15118. > Fix TestDelegationToken

[jira] [Commented] (HDFS-15111) stopStandbyServices() should log which service state it is transitioning from.

[ https://issues.apache.org/jira/browse/HDFS-15111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035513#comment-17035513 ] Ayush Saxena commented on HDFS-15111: - Just that the {{stopActiveServices()}} to logs

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

Ayush Saxena created HDFS-15167: --- Summary: Block Report Interval shouldn't be reset apart from first Block Report Key: HDFS-15167 URL: https://issues.apache.org/jira/browse/HDFS-15167 Project: Hadoop HD

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036013#comment-17036013 ] Ayush Saxena commented on HDFS-15167: - The {{resetBlockReportTime}} should be set tru

[jira] [Updated] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15164: Attachment: HDFS-15164-02.patch > Fix TestDelegationTokensWithHA > -- >

[jira] [Commented] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036317#comment-17036317 ] Ayush Saxena commented on HDFS-15164: - Thanx [~elgoiri] [~vagarychen] Have fixed the

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15167: Status: Patch Available (was: Open) > Block Report Interval shouldn't be reset apart from first Bl

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

[ 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-01.patch > Block Report Interval shouldn't be reset apart from first Block R

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

[ 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-02.patch > Block Report Interval shouldn't be reset apart from first Block R

[jira] [Created] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

Ayush Saxena created HDFS-15170: --- Summary: EC: Block gets marked as CORRUPT in case of failover and pipeline recovery Key: HDFS-15170 URL: https://issues.apache.org/jira/browse/HDFS-15170 Project: Hadoo

[jira] [Updated] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15170: Attachment: HDFS-15170-01.patch > EC: Block gets marked as CORRUPT in case of failover and pipeline

[jira] [Updated] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15170: Status: Patch Available (was: Open) > EC: Block gets marked as CORRUPT in case of failover and pip

[jira] [Commented] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037104#comment-17037104 ] Ayush Saxena commented on HDFS-15170: - To repro using the test : just change this lin

[jira] [Comment Edited] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037104#comment-17037104 ] Ayush Saxena edited comment on HDFS-15170 at 2/14/20 4:34 PM: -

[jira] [Updated] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15164: Fix Version/s: 2.10.1 3.2.2 3.1.4 3.3.0

[jira] [Commented] (HDFS-15164) Fix TestDelegationTokensWithHA

[ https://issues.apache.org/jira/browse/HDFS-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037113#comment-17037113 ] Ayush Saxena commented on HDFS-15164: - Committed to trunk, branch-3.2,3.1 and 2.10 Th

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037121#comment-17037121 ] Ayush Saxena edited comment on HDFS-15167 at 2/14/20 5:14 PM: -

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037121#comment-17037121 ] Ayush Saxena commented on HDFS-15167: - Couple of test failures, fixed in v2 just unse

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037152#comment-17037152 ] Ayush Saxena commented on HDFS-15167: - Still couple of failures, some problem with {{

[jira] [Commented] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037482#comment-17037482 ] Ayush Saxena commented on HDFS-15170: - Test failures not related. > EC: Block gets m

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

[ 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-03.patch > Block Report Interval shouldn't be reset apart from first Block R

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

[ 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-04.patch > Block Report Interval shouldn't be reset apart from first Block R

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

[ 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-05.patch > Block Report Interval shouldn't be reset apart from first Block R

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037694#comment-17037694 ] Ayush Saxena commented on HDFS-15167: - FIxed all the the tests, were failing due to w

[jira] [Updated] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15115: Fix Version/s: 3.1.4 > Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically

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

[ 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-06.patch > Block Report Interval shouldn't be reset apart from first Block R

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037749#comment-17037749 ] Ayush Saxena commented on HDFS-15167: - Thanx [~surendrasingh] for the review. Well i

[jira] [Updated] (HDFS-15170) EC: Block gets marked as CORRUPT in case of failover and pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15170: Attachment: HDFS-15170-02.patch > EC: Block gets marked as CORRUPT in case of failover and pipeline

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

[ 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 R

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038360#comment-17038360 ] Ayush Saxena commented on HDFS-15167: - Thanx [~elgoiri] for the review. Added comment

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

[ https://issues.apache.org/jira/browse/HDFS-15104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038373#comment-17038373 ] Ayush Saxena commented on HDFS-15104: - How can u say that block is corrupt, if no dat

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

[ 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 R

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038573#comment-17038573 ] Ayush Saxena commented on HDFS-15167: - Handled in v8 > Block Report Interval shouldn

[jira] [Updated] (HDFS-13739) Add option to disable rack local write preference

[ https://issues.apache.org/jira/browse/HDFS-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-13739: Summary: Add option to disable rack local write preference (was: Option to disable Rack Local Writ

[jira] [Updated] (HDFS-13739) Add option to disable rack local write preference

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

[jira] [Commented] (HDFS-13739) Add option to disable rack local write preference

[ https://issues.apache.org/jira/browse/HDFS-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039667#comment-17039667 ] Ayush Saxena commented on HDFS-13739: - Committed to trunk. Thanx [~vinayakumarb] for

[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&focusedCommentId=17039673#comment-17039673 ] Ayush Saxena commented on HDFS-15182: - can we do the init in {{@Before}}? > TestBloc

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

[ https://issues.apache.org/jira/browse/HDFS-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039928#comment-17039928 ] Ayush Saxena commented on HDFS-15167: - Thanx [~elgoiri] for the review!!! [~surendras

[jira] [Updated] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15115: Fix Version/s: 2.10.1 > Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamicall

[jira] [Commented] (HDFS-15115) Namenode crash caused by NPE in BlockPlacementPolicyDefault when dynamically change logger to debug

[ https://issues.apache.org/jira/browse/HDFS-15115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040179#comment-17040179 ] Ayush Saxena commented on HDFS-15115: - Cherry-picked to branch-2.10 > Namenode crash

[jira] [Updated] (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:all-tabpanel ] Ayush Saxena updated HDFS-15186: Status: Patch Available (was: Open) > Erasure Coding: Decommission may generate the parity block's

[jira] [Assigned] (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:all-tabpanel ] Ayush Saxena reassigned HDFS-15186: --- Assignee: Yao Guangdong > Erasure Coding: Decommission may generate the parity block's conte

[jira] [Created] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

Ayush Saxena created HDFS-15187: --- Summary: CORRUPT replica mismatch between namenodes after failover Key: HDFS-15187 URL: https://issues.apache.org/jira/browse/HDFS-15187 Project: Hadoop HDFS I

[jira] [Updated] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15187: Attachment: HDFS-15187-01.patch > CORRUPT replica mismatch between namenodes after failover > -

[jira] [Updated] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15187: Status: Patch Available (was: Open) > CORRUPT replica mismatch between namenodes after failover >

[jira] [Updated] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15187: Attachment: (was: HDFS-15187-02.patch) > CORRUPT replica mismatch between namenodes after failo

[jira] [Updated] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15187: Attachment: HDFS-15187-02.patch > CORRUPT replica mismatch between namenodes after failover > -

[jira] [Updated] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15187: Attachment: HDFS-15187-02.patch > CORRUPT replica mismatch between namenodes after failover > -

[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&focusedCommentId=17041633#comment-17041633 ] Ayush Saxena commented on HDFS-15182: - Jenkins seems having complains. Have triggered

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

[ https://issues.apache.org/jira/browse/HDFS-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041688#comment-17041688 ] Ayush Saxena commented on HDFS-15120: - I am not catching what is the problem with jus

[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&focusedCommentId=17041783#comment-17041783 ] Ayush Saxena commented on HDFS-15182: - There are three tests modified and the descrip

[jira] [Updated] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15187: Attachment: HDFS-15187-03.patch > CORRUPT replica mismatch between namenodes after failover > -

[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&focusedCommentId=17041897#comment-17041897 ] Ayush Saxena commented on HDFS-15182: - The other two tests are passing without your f

[jira] [Commented] (HDFS-14731) [FGL] Remove redundant locking on NameNode.

[ https://issues.apache.org/jira/browse/HDFS-14731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041908#comment-17041908 ] Ayush Saxena commented on HDFS-14731: - Thanx [~shv] for the work here. v001 LGTM +1

[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&focusedCommentId=17042014#comment-17042014 ] Ayush Saxena commented on HDFS-15182: - If the tests are passing without this change.

[jira] [Commented] (HDFS-15154) Allow only hdfs superusers the ability to assign HDFS storage policies

[ https://issues.apache.org/jira/browse/HDFS-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042114#comment-17042114 ] Ayush Saxena commented on HDFS-15154: - Thanx [~swagle] for the patch. To handle dep

[jira] [Comment Edited] (HDFS-15154) Allow only hdfs superusers the ability to assign HDFS storage policies

[ https://issues.apache.org/jira/browse/HDFS-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042114#comment-17042114 ] Ayush Saxena edited comment on HDFS-15154 at 2/21/20 7:13 PM: -

[jira] [Commented] (HDFS-15154) Allow only hdfs superusers the ability to assign HDFS storage policies

[ https://issues.apache.org/jira/browse/HDFS-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042154#comment-17042154 ] Ayush Saxena commented on HDFS-15154: - {{conf.getBoolean(DFSConfigKeys.DFS_STORAGE_PO

[jira] [Comment Edited] (HDFS-15154) Allow only hdfs superusers the ability to assign HDFS storage policies

[ https://issues.apache.org/jira/browse/HDFS-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042154#comment-17042154 ] Ayush Saxena edited comment on HDFS-15154 at 2/21/20 8:24 PM: -

[jira] [Commented] (HDFS-15187) CORRUPT replica mismatch between namenodes after failover

[ https://issues.apache.org/jira/browse/HDFS-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042373#comment-17042373 ] Ayush Saxena commented on HDFS-15187: - Thanx [~elgoiri] and [~vinayakumarb] for the r

[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&focusedCommentId=17042403#comment-17042403 ] Ayush Saxena commented on HDFS-15186: - Shouldn't we fix, this at namenode side? The E

[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&focusedCommentId=17042415#comment-17042415 ] Ayush Saxena commented on HDFS-15182: - v004 LGTM +1 > TestBlockManager#testOneOfTwoR

[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&focusedCommentId=17042458#comment-17042458 ] Ayush Saxena commented on HDFS-15186: - HDFS-14768 tend to make a busy live DN to be c

[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: Resolve

[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&focusedCommentId=17042465#comment-17042465 ] Ayush Saxena commented on HDFS-15182: - Committed to trunk. Thanx [~leosun08] for the

[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&focusedCommentId=17042631#comment-17042631 ] Ayush Saxena commented on HDFS-15176: - Thanx [~LiJinglun] for the patch. nit : In the

[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&focusedCommentId=17042695#comment-17042695 ] Ayush Saxena commented on HDFS-15124: - Thanx Everyone for the work here. [~ctest.tea

[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&focusedCommentId=17042696#comment-17042696 ] Ayush Saxena commented on HDFS-15114: - Thanx [~Steven Rand]  for the report. Are you

<    3   4   5   6   7   8   9   10   11   12   >