[jira] [Created] (HDFS-15394) Add all available fs.viewfs.overload.scheme.target..impl classes in core-default.xml bydefault.

Uma Maheswara Rao G created HDFS-15394: -- Summary: Add all available fs.viewfs.overload.scheme.target..impl classes in core-default.xml bydefault. Key: HDFS-15394 URL:

[jira] [Updated] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-15389: --- Parent: HDFS-15289 Issue Type: Sub-task (was: Bug) > DFSAdmin should close

[jira] [Commented] (HDFS-15321) Make DFSAdmin tool to work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127019#comment-17127019 ] Uma Maheswara Rao G commented on HDFS-15321: Thanks for reporting it [~ayushtkn], I have

[jira] [Commented] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127005#comment-17127005 ] Ayush Saxena commented on HDFS-15389: - Have fixed the checkstyle in PR

[jira] [Commented] (HDFS-15330) Document the ViewFSOverloadScheme details in ViewFS guide

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

[jira] [Updated] (HDFS-15330) Document the ViewFSOverloadScheme details in ViewFS guide

[ https://issues.apache.org/jira/browse/HDFS-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-15330: --- Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed

[jira] [Commented] (HDFS-15393) Review of PendingReconstructionBlocks

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

[jira] [Updated] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15389: Description: Two Issues Here : Firstly Prior to HDFS-15321, When DFSAdmin was closed the

[jira] [Commented] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126883#comment-17126883 ] Ayush Saxena commented on HDFS-15390: - Can you extend a UT for the issue? > client fails forever

[jira] [Comment Edited] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126638#comment-17126638 ] Sean Chow edited comment on HDFS-15390 at 6/5/20, 2:57 PM: --- It's easy to

[jira] [Commented] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126837#comment-17126837 ] Sean Chow commented on HDFS-15390: -- Patch attached. Now we can see the exception is ignored when

[jira] [Updated] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Chow updated HDFS-15390: - Attachment: HDFS-15390.01.patch > client fails forever when namenode ipaddr changed >

[jira] [Created] (HDFS-15393) Review of PendingReconstructionBlocks

David Mollitor created HDFS-15393: - Summary: Review of PendingReconstructionBlocks Key: HDFS-15393 URL: https://issues.apache.org/jira/browse/HDFS-15393 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-15359) EC: Allow closing a file with committed blocks

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

[jira] [Updated] (HDFS-15359) EC: Allow closing a file with committed blocks

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

[jira] [Commented] (HDFS-15359) EC: Allow closing a file with committed blocks

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

[jira] [Commented] (HDFS-15351) Blocks Scheduled Count was wrong on Truncate

[ https://issues.apache.org/jira/browse/HDFS-15351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126748#comment-17126748 ] David Mollitor commented on HDFS-15351: --- Thanks for pinging me [~hemanthboyina] a few times. I have

[jira] [Updated] (HDFS-15391) Standby NameNode cannot load the edit log correctly due to edit log corruption, resulting in the service exiting abnormally and unable to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Summary: Standby NameNode cannot load the edit log correctly due to edit log corruption, resulting in

[jira] [Commented] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126740#comment-17126740 ] huhaiyang commented on HDFS-15391: -- [~ayushtkn] Thank you for reply {quote} These are two different

[jira] [Comment Edited] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126730#comment-17126730 ] Ayush Saxena edited comment on HDFS-15391 at 6/5/20, 12:31 PM: --- Thanx,

[jira] [Created] (HDFS-15392) DistrbutedFileSystem#concat api can create large number of small blocks

Lokesh Jain created HDFS-15392: -- Summary: DistrbutedFileSystem#concat api can create large number of small blocks Key: HDFS-15392 URL: https://issues.apache.org/jira/browse/HDFS-15392 Project: Hadoop

[jira] [Comment Edited] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126724#comment-17126724 ] huhaiyang edited comment on HDFS-15391 at 6/5/20, 12:31 PM: Standby NameNode 

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Commented] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126730#comment-17126730 ] Ayush Saxena commented on HDFS-15391: - Thanx, These are two different traces, correct? You tried

[jira] [Updated] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Chow updated HDFS-15390: - Description: For machine replacement, I replace my standby namenode with a new ipaddr and keep the same

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Commented] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126724#comment-17126724 ] huhaiyang commented on HDFS-15391: -- Standby NameNode  exception log： 2020-06-04 18:32:11,561 ERROR

[jira] [Commented] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126723#comment-17126723 ] Ayush Saxena commented on HDFS-15391: - Do you have backported HDFS-7663 in that? If yes, HDFS-14581

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Commented] (HDFS-13179) TestLazyPersistReplicaRecovery#testDnRestartWithSavedReplicas fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126722#comment-17126722 ] Stephen O'Donnell commented on HDFS-13179: -- Ah good to know. Seems I have been wasting some time

[jira] [Updated] (HDFS-13179) TestLazyPersistReplicaRecovery#testDnRestartWithSavedReplicas fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-13179: - Attachment: HDFS-13179-branch-3.0.003.patch >

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Description: In the cluster version 3.2.0 production environment， We found that due to edit log

[jira] [Updated] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in abnormal exit of the service and failure to restart

[ https://issues.apache.org/jira/browse/HDFS-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huhaiyang updated HDFS-15391: - Summary: Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, result in

[jira] [Created] (HDFS-15391) Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, resulting in abnormal exit of the service and failure to restart

huhaiyang created HDFS-15391: Summary: Due to edit log corruption, Standby NameNode could not properly load the Ediltog log, resulting in abnormal exit of the service and failure to restart Key: HDFS-15391 URL:

[jira] [Commented] (HDFS-13179) TestLazyPersistReplicaRecovery#testDnRestartWithSavedReplicas fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126718#comment-17126718 ] Ayush Saxena commented on HDFS-13179: - branch-3.0 is EOL?

[jira] [Updated] (HDFS-15386) ReplicaNotFoundException keeps happening in DN after removing multiple DN's data directories

[ https://issues.apache.org/jira/browse/HDFS-15386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-15386: - Fix Version/s: 3.1.5 3.4.0 3.3.1

[jira] [Commented] (HDFS-15386) ReplicaNotFoundException keeps happening in DN after removing multiple DN's data directories

[ https://issues.apache.org/jira/browse/HDFS-15386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126715#comment-17126715 ] Stephen O'Donnell commented on HDFS-15386: -- Please create a PR for branch-2.10 and then we can

[jira] [Commented] (HDFS-13179) TestLazyPersistReplicaRecovery#testDnRestartWithSavedReplicas fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126713#comment-17126713 ] Stephen O'Donnell commented on HDFS-13179: -- This is now reverted from branch-3.0. I will post a

[jira] [Commented] (HDFS-15386) ReplicaNotFoundException keeps happening in DN after removing multiple DN's data directories

[ https://issues.apache.org/jira/browse/HDFS-15386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126647#comment-17126647 ] Toshihiro Suzuki commented on HDFS-15386: - [~sodonnell] Thank you for merging the PR to trunk!

[jira] [Commented] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126638#comment-17126638 ] Sean Chow commented on HDFS-15390: -- There 's two way to fix this:  # When updateAddress is true, do not

[jira] [Commented] (HDFS-15386) ReplicaNotFoundException keeps happening in DN after removing multiple DN's data directories

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

[jira] [Updated] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Chow updated HDFS-15390: - Description: For machine replacement, I replace my standby namenode with a new ipaddr and keep the same

[jira] [Commented] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

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

[jira] [Updated] (HDFS-15390) client fails forever when namenode ipaddr changed

[ https://issues.apache.org/jira/browse/HDFS-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Chow updated HDFS-15390: - Description: For machine replacement, I replace my standby namenode with a new ipaddr and keep the same

[jira] [Created] (HDFS-15390) client fails forever when namenode ipaddr changed

Sean Chow created HDFS-15390: Summary: client fails forever when namenode ipaddr changed Key: HDFS-15390 URL: https://issues.apache.org/jira/browse/HDFS-15390 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126436#comment-17126436 ] Ayush Saxena commented on HDFS-15389: - [~umamaheswararao] / [~rakeshr] / [~vinayakumarb] can you

[jira] [Commented] (HDFS-15321) Make DFSAdmin tool to work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126430#comment-17126430 ] Ayush Saxena commented on HDFS-15321: - There was one more problem here. {{DFSAdmin

[jira] [Updated] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15389: Attachment: HDFS-15389-01.patch > DFSAdmin should close filesystem and dfsadmin

[jira] [Updated] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

[ https://issues.apache.org/jira/browse/HDFS-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-15389: Status: Patch Available (was: Open) > DFSAdmin should close filesystem and dfsadmin

[jira] [Created] (HDFS-15389) DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme

Ayush Saxena created HDFS-15389: --- Summary: DFSAdmin should close filesystem and dfsadmin -setBalancerBandwidth should work with ViewFSOverloadScheme Key: HDFS-15389 URL: