[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Description: ConcurrentModificationException error happens on NameNode occasionally.   {code:java}

[jira] [Created] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

Daniel Ma created HDFS-15796: Summary: ConcurrentModificationException error happens on NameNode occasionally Key: HDFS-15796 URL: https://issues.apache.org/jira/browse/HDFS-15796 Project: Hadoop HDFS

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: 0002-HDFS-15796.patch > ConcurrentModificationException error happens on NameNode

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: (was: 0001-HDFS-15796.patch) > ConcurrentModificationException error happens on NameNode

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: (was: 0002-HDFS-15796.patch) > ConcurrentModificationException error happens on NameNode

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: (was: 0003-HDFS-15796.patch) > ConcurrentModificationException error happens on NameNode

[jira] [Commented] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376571#comment-17376571 ] Daniel Ma commented on HDFS-16115: -- hello [~hexiaoqiao]. Thanks for review,  1-For non-fatal error, I

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: HDFS-15796-0001.patch > ConcurrentModificationException error happens on NameNode

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376586#comment-17376586 ] Daniel Ma edited comment on HDFS-15796 at 7/7/21, 1:52 PM: --- [~sodonnell] Yes,

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376586#comment-17376586 ] Daniel Ma commented on HDFS-15796: -- [~sodonnell] Yes, it is more elegant. >

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376429#comment-17376429 ] Daniel Ma edited comment on HDFS-15796 at 7/7/21, 11:57 AM: [~sodonnell]

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: 0003-HDFS-15796.patch > ConcurrentModificationException error happens on NameNode

[jira] [Assigned] (HDFS-16117) Add file count info in audit log to record the file count for delete and getListing RPC request to assist user trouble shooting when RPC cost is increasing

[ https://issues.apache.org/jira/browse/HDFS-16117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma reassigned HDFS-16117: Assignee: Daniel Ma > Add file count info in audit log to record the file count for delete and >

[jira] [Assigned] (HDFS-16093) DataNodes under decommission will still be returned to the client via getLocatedBlocks, so the client may request decommissioning datanodes to read which will cause badl

[ https://issues.apache.org/jira/browse/HDFS-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma reassigned HDFS-16093: Assignee: Daniel Ma > DataNodes under decommission will still be returned to the client via >

[jira] [Assigned] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma reassigned HDFS-16115: Assignee: Daniel Ma > Asynchronously handle BPServiceActor command mechanism may result in >

[jira] [Commented] (HDFS-16117) Add file count info in audit log to record the file count for delete and getListing RPC request to assist user trouble shooting when RPC cost is increasing

[ https://issues.apache.org/jira/browse/HDFS-16117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376938#comment-17376938 ] Daniel Ma commented on HDFS-16117: -- Hello ，[~sodonnell] Could you pls help to review this patch? > Add

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17377326#comment-17377326 ] Daniel Ma commented on HDFS-15796: -- [~sodonnell] Yes， NameNode will exit when the exception happens

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370995#comment-17370995 ] Daniel Ma commented on HDFS-15796: -- [~weichiu]  No idea what kind of condition can reproduce this

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370995#comment-17370995 ] Daniel Ma edited comment on HDFS-15796 at 6/29/21, 2:35 AM: [~weichiu]  No

[jira] [Updated] (HDFS-16094) HDFS start failed owing to daemon pid file is not cleared in some exception senario

[ https://issues.apache.org/jira/browse/HDFS-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16094: - Summary: HDFS start failed owing to daemon pid file is not cleared in some exception senario (was:

[jira] [Created] (HDFS-16094) NameNode start failed owing to daemon pid file is not cleared in some exception senario

Daniel Ma created HDFS-16094: Summary: NameNode start failed owing to daemon pid file is not cleared in some exception senario Key: HDFS-16094 URL: https://issues.apache.org/jira/browse/HDFS-16094

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370995#comment-17370995 ] Daniel Ma edited comment on HDFS-15796 at 6/29/21, 2:36 AM: [~weichiu]  No

[jira] [Created] (HDFS-16093) DataNodes under decommission will still be returned to the client via getLocatedBlocks, so the client may request decommissioning datanodes to read which will cause badly

Daniel Ma created HDFS-16093: Summary: DataNodes under decommission will still be returned to the client via getLocatedBlocks, so the client may request decommissioning datanodes to read which will cause badly competation on disk IO.

[jira] [Commented] (HDFS-16093) DataNodes under decommission will still be returned to the client via getLocatedBlocks, so the client may request decommissioning datanodes to read which will cause bad

[ https://issues.apache.org/jira/browse/HDFS-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371015#comment-17371015 ] Daniel Ma commented on HDFS-16093: -- Hi [~tomscut], thanks for your quick reply. The Jira you mentioned

[jira] [Updated] (HDFS-16094) HDFS balancer process start failed owing to daemon pid file is not cleared in some exception senario

[ https://issues.apache.org/jira/browse/HDFS-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16094: - Description: HDFS balancer process start failed owing to daemon pid file is not cleared in some

[jira] [Updated] (HDFS-16094) HDFS balancer process start failed owing to daemon pid file is not cleared in some exception senario

[ https://issues.apache.org/jira/browse/HDFS-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16094: - Summary: HDFS balancer process start failed owing to daemon pid file is not cleared in some exception

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370997#comment-17370997 ] Daniel Ma commented on HDFS-15796: -- [~sodonnell] We have made some modifications based on OS version,

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370995#comment-17370995 ] Daniel Ma edited comment on HDFS-15796 at 6/29/21, 2:33 AM: [~weichiu]  No

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370995#comment-17370995 ] Daniel Ma edited comment on HDFS-15796 at 6/29/21, 2:34 AM: [~weichiu]  No

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370995#comment-17370995 ] Daniel Ma edited comment on HDFS-15796 at 6/29/21, 2:32 AM: [~weichiu]  No

[jira] [Commented] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376146#comment-17376146 ] Daniel Ma commented on HDFS-16115: -- [~hexiaoqiao] Thanks for your review and tips. Actually the issue

[jira] [Updated] (HDFS-16094) HDFS balancer process start failed owing to daemon pid file is not cleared in some exception senario

[ https://issues.apache.org/jira/browse/HDFS-16094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16094: - Target Version/s: 3.1.1 (was: 3.4.0) > HDFS balancer process start failed owing to daemon pid file is

[jira] [Comment Edited] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375401#comment-17375401 ] Daniel Ma edited comment on HDFS-16115 at 7/7/21, 1:46 AM: --- Hello

[jira] [Comment Edited] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375401#comment-17375401 ] Daniel Ma edited comment on HDFS-16115 at 7/7/21, 1:47 AM: --- Hello

[jira] [Comment Edited] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376146#comment-17376146 ] Daniel Ma edited comment on HDFS-16115 at 7/7/21, 2:01 AM: --- [~hexiaoqiao] 

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16117) Add file count info in audit log to record the file count count in delete and getListing RPC request to assist user trouble shooting when RPC cost is increasing

[ https://issues.apache.org/jira/browse/HDFS-16117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16117: - Attachment: 0001-HDFS-16117.patch > Add file count info in audit log to record the file count count in

[jira] [Created] (HDFS-16117) Add file count info in audit log to record the file count count in delete and getListing RPC request to assist user trouble shooting when RPC cost is increasing

Daniel Ma created HDFS-16117: Summary: Add file count info in audit log to record the file count count in delete and getListing RPC request to assist user trouble shooting when RPC cost is increasing Key: HDFS-16117

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376429#comment-17376429 ] Daniel Ma commented on HDFS-15796: -- [~sodonnell] yes, I totally agree with the solution you raised. I

[jira] [Updated] (HDFS-16117) Add file count info in audit log to record the file count for delete and getListing RPC request to assist user trouble shooting when RPC cost is increasing

[ https://issues.apache.org/jira/browse/HDFS-16117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16117: - Summary: Add file count info in audit log to record the file count for delete and getListing RPC request

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Attachment: 0001-HDFS-16115.patch > Asynchronously handle BPServiceActor command mechanism may result in

[jira] [Commented] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375401#comment-17375401 ] Daniel Ma commented on HDFS-16115: -- [~brahmareddy] [~ayush] Pls help to review this patch. >

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Attachment: 0001-HDFS-15796.patch > ConcurrentModificationException error happens on NameNode

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375331#comment-17375331 ] Daniel Ma commented on HDFS-15796: -- [~weichiu],[~hexiaoqiao]  Pls help to review this patch, thanks >

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Comment Edited] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375401#comment-17375401 ] Daniel Ma edited comment on HDFS-16115 at 7/6/21, 9:33 AM: --- Hello

[jira] [Updated] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-15796: - Target Version/s: 3.3.1 (was: 3.4.0) > ConcurrentModificationException error happens on NameNode

[jira] [Created] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

Daniel Ma created HDFS-16115: Summary: Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error. Key: HDFS-16115 URL:

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Commented] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375421#comment-17375421 ] Daniel Ma commented on HDFS-15796: -- [~sodonnell] Thanks for reviewing, Actually you missed the for loop

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Updated] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16115: - Description: It is an improvement issue. Actually the issue has two sub issues: 1- BPServerActor thread

[jira] [Comment Edited] (HDFS-15796) ConcurrentModificationException error happens on NameNode occasionally

[ https://issues.apache.org/jira/browse/HDFS-15796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375421#comment-17375421 ] Daniel Ma edited comment on HDFS-15796 at 7/6/21, 9:57 AM: --- [~sodonnell]

[jira] [Commented] (HDFS-16098) ERROR tools.DiskBalancerCLI: java.lang.IllegalArgumentException

[ https://issues.apache.org/jira/browse/HDFS-16098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17375427#comment-17375427 ] Daniel Ma commented on HDFS-16098: -- [~wangyanfu] Thanks for reporting this issue. Could you pls share

[jira] [Commented] (HDFS-16060) There is an inconsistent between replicas of datanodes when hardware is abnormal

[ https://issues.apache.org/jira/browse/HDFS-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535888#comment-17535888 ] Daniel Ma commented on HDFS-16060: -- [~ferhui]  Thanks for your report, I have encountered the similiar

[jira] [Comment Edited] (HDFS-16060) There is an inconsistent between replicas of datanodes when hardware is abnormal

[ https://issues.apache.org/jira/browse/HDFS-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535888#comment-17535888 ] Daniel Ma edited comment on HDFS-16060 at 5/12/22 6:22 AM: --- [~ferhui]  Thanks

[jira] [Comment Edited] (HDFS-16060) There is an inconsistent between replicas of datanodes when hardware is abnormal

[ https://issues.apache.org/jira/browse/HDFS-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535888#comment-17535888 ] Daniel Ma edited comment on HDFS-16060 at 5/12/22 6:27 AM: --- [~ferhui]  Thanks

[jira] [Created] (HDFS-16869) DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak

Daniel Ma created HDFS-16869: Summary: DelegationTokenRenewer timeout feature may cause high utilization of CPU and object leak Key: HDFS-16869 URL: https://issues.apache.org/jira/browse/HDFS-16869

[jira] [Created] (HDFS-16870) Client ip should also be recorded when NameNode is processing reportBadBlocks

Daniel Ma created HDFS-16870: Summary: Client ip should also be recorded when NameNode is processing reportBadBlocks Key: HDFS-16870 URL: https://issues.apache.org/jira/browse/HDFS-16870 Project: Hadoop

[jira] [Updated] (HDFS-16870) Client ip should also be recorded when NameNode is processing reportBadBlocks

[ https://issues.apache.org/jira/browse/HDFS-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16870: - Description: There are two scenario involved for reportBadBlocks. 1-HDFS client will report bad block to

[jira] [Updated] (HDFS-16869) Fail to start namenode owing to 0 size of clientid recorded in edit log.

[ https://issues.apache.org/jira/browse/HDFS-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16869: - Description: We first encounter this issue in 3.3.1 version when we are upgrading from 3.1.1 to 3.3.1

[jira] [Updated] (HDFS-16870) Client ip should also be recorded when NameNode is processing reportBadBlocks

[ https://issues.apache.org/jira/browse/HDFS-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16870: - Description: There are two scenario involved for reportBadBlocks. 1-HDFS client will report bad block to

[jira] [Updated] (HDFS-16869) Fail to start namenode owing to 0 size of clientid recorded in edit log.

[ https://issues.apache.org/jira/browse/HDFS-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16869: - Summary: Fail to start namenode owing to 0 size of clientid recorded in edit log. (was:

[jira] [Updated] (HDFS-16869) Fail to start namenode owing to 0 size of clientid recorded in edit log.

[ https://issues.apache.org/jira/browse/HDFS-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16869: - Issue Type: Bug (was: Improvement) > Fail to start namenode owing to 0 size of clientid recorded in

[jira] [Updated] (HDFS-16869) Fail to start namenode owing to 0 size of clientid recorded in edit log.

[ https://issues.apache.org/jira/browse/HDFS-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16869: - Description: The root cause for why 0 size of clientid happened here is still not found. So here we add

[jira] [Assigned] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

[ https://issues.apache.org/jira/browse/HDFS-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma reassigned HDFS-16871: Assignee: Daniel Ma > DiskBalancer process may throws IllegalArgumentException when the target >

[jira] [Created] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

Daniel Ma created HDFS-16871: Summary: DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname Key: HDFS-16871 URL:

[jira] [Updated] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

[ https://issues.apache.org/jira/browse/HDFS-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16871: - Attachment: screenshot-1.png > DiskBalancer process may throws IllegalArgumentException when the target

[jira] [Updated] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

[ https://issues.apache.org/jira/browse/HDFS-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16871: - Description: DiskBalancer process read DataNode hostname as lowercase letters, !screenshot-1.png! but

[jira] [Updated] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

[ https://issues.apache.org/jira/browse/HDFS-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16871: - Description: DiskBalancer process read DataNode hostname as lowercase letters, !screenshot-1.png! but

[jira] [Updated] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

[ https://issues.apache.org/jira/browse/HDFS-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16871: - Description: DiskBalancer process read DataNode hostname as lowercase letters, !screenshot-1.png! but

[jira] [Updated] (HDFS-16871) DiskBalancer process may throws IllegalArgumentException when the target DataNode has capital letter in hostname

[ https://issues.apache.org/jira/browse/HDFS-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Ma updated HDFS-16871: - Attachment: screenshot-2.png > DiskBalancer process may throws IllegalArgumentException when the target

[jira] [Commented] (HDFS-16115) Asynchronously handle BPServiceActor command mechanism may result in BPServiceActor never fails even CommandProcessingThread is closed with fatal error.

[ https://issues.apache.org/jira/browse/HDFS-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651129#comment-17651129 ] Daniel Ma commented on HDFS-16115: -- [~hemanthboyina] [~brahma] Could you pls help to review >

[jira] [Commented] (HDFS-13224) RBF: Resolvers to support mount points across multiple subclusters

[ https://issues.apache.org/jira/browse/HDFS-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17689432#comment-17689432 ] Daniel Ma commented on HDFS-13224: -- [~elgoiri] Could you pls share the design doc for this feature. No