[jira] [Work logged] (HDDS-1710) Publish JVM metrics via Hadoop metrics

[ https://issues.apache.org/jira/browse/HDDS-1710?focusedWorklogId=276379=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276379 ] ASF GitHub Bot logged work on HDDS-1710: Author: ASF GitHub Bot

[jira] [Commented] (HDFS-13843) RBF: When we add/update mount entry to multiple destinations, unable to see the order information in mount entry points and in federation router UI

[ https://issues.apache.org/jira/browse/HDFS-13843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884671#comment-16884671 ] Ayush Saxena commented on HDFS-13843: - bq. hdfs dfsrouteradmin -update /apps1 hacluster

[jira] [Commented] (HDFS-13843) RBF: When we add/update mount entry to multiple destinations, unable to see the order information in mount entry points and in federation router UI

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

[jira] [Updated] (HDFS-14645) ViewFileSystem should close the child FileSystems in close()

[ https://issues.apache.org/jira/browse/HDFS-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jihyun Cho updated HDFS-14645: -- Attachment: HDFS-14645.001.patch > ViewFileSystem should close the child FileSystems in close() >

[jira] [Created] (HDFS-14645) ViewFileSystem should close the child FileSystems in close()

Jihyun Cho created HDFS-14645: - Summary: ViewFileSystem should close the child FileSystems in close() Key: HDFS-14645 URL: https://issues.apache.org/jira/browse/HDFS-14645 Project: Hadoop HDFS

[jira] [Created] (HDDS-1796) SCMClientProtocolServer#getContainerWithPipeline should check for admin access

Mukul Kumar Singh created HDDS-1796: --- Summary: SCMClientProtocolServer#getContainerWithPipeline should check for admin access Key: HDDS-1796 URL: https://issues.apache.org/jira/browse/HDDS-1796

[jira] [Updated] (HDFS-14645) ViewFileSystem should close the child FileSystems in close()

[ https://issues.apache.org/jira/browse/HDFS-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayush Saxena updated HDFS-14645: Status: Patch Available (was: Open) > ViewFileSystem should close the child FileSystems in

[jira] [Commented] (HDFS-13693) Remove unnecessary search in INodeDirectory.addChild during image loading

[ https://issues.apache.org/jira/browse/HDFS-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884688#comment-16884688 ] He Xiaoqiao commented on HDFS-13693: [~leosun08], Thanks for your comments. Maybe my review comments

[jira] [Work logged] (HDDS-1710) Publish JVM metrics via Hadoop metrics

[ https://issues.apache.org/jira/browse/HDDS-1710?focusedWorklogId=276391=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276391 ] ASF GitHub Bot logged work on HDDS-1710: Author: ASF GitHub Bot

[jira] [Work logged] (HDDS-1710) Publish JVM metrics via Hadoop metrics

[ https://issues.apache.org/jira/browse/HDDS-1710?focusedWorklogId=276390=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276390 ] ASF GitHub Bot logged work on HDDS-1710: Author: ASF GitHub Bot

[jira] [Commented] (HDFS-13571) Dead DataNode Detector

[ https://issues.apache.org/jira/browse/HDFS-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884704#comment-16884704 ] Yiqun Lin commented on HDFS-13571: -- Thanks for the summary, [~leosun08]. Design almost looks good to me

[jira] [Comment Edited] (HDFS-13571) Dead DataNode Detector

[ https://issues.apache.org/jira/browse/HDFS-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884704#comment-16884704 ] Yiqun Lin edited comment on HDFS-13571 at 7/14/19 3:47 PM: --- Thanks for the

[jira] [Commented] (HDFS-14631) The DirectoryScanner doesn't fix the wrongly placed replica.

[ https://issues.apache.org/jira/browse/HDFS-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884709#comment-16884709 ] He Xiaoqiao commented on HDFS-14631: [~LiJinglun], Thanks for report and patch this issue. Some

[jira] [Commented] (HDFS-13571) Dead DataNode Detector

[ https://issues.apache.org/jira/browse/HDFS-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884724#comment-16884724 ] He Xiaoqiao commented on HDFS-13571: Thanks [~leosun08] for your involves. Just quick review the

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Description: *Problem Description:* In the multi-NameNode scenario, when a SNN uploads a FsImage, it

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Description: *Problem Description:* In the multi-NameNode scenario, when a SNN uploads a FsImage, it

[jira] [Commented] (HDFS-11246) FSNameSystem#logAuditEvent should be called outside the read or write locks

[ https://issues.apache.org/jira/browse/HDFS-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884847#comment-16884847 ] He Xiaoqiao commented on HDFS-11246: submit new patch [^HDFS-11246.009.patch] and fix failure unit

[jira] [Updated] (HDFS-11246) FSNameSystem#logAuditEvent should be called outside the read or write locks

[ https://issues.apache.org/jira/browse/HDFS-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] He Xiaoqiao updated HDFS-11246: --- Attachment: HDFS-11246.009.patch > FSNameSystem#logAuditEvent should be called outside the read or

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Attachment: (was: get2.png) > Standby NameNode should terminate the FsImage put process as soon as

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Attachment: get2.png > Standby NameNode should terminate the FsImage put process as soon as possible

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Description: *Problem Description:* In the multi-NameNode scenario, when a SNN uploads a FsImage, it

[jira] [Commented] (HDFS-14645) ViewFileSystem should close the child FileSystems in close()

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

[jira] [Updated] (HDFS-14631) The DirectoryScanner doesn't fix the wrongly placed replica.

[ https://issues.apache.org/jira/browse/HDFS-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinglun updated HDFS-14631: --- Attachment: HDFS-14631.002.patch > The DirectoryScanner doesn't fix the wrongly placed replica. >

[jira] [Commented] (HDFS-14631) The DirectoryScanner doesn't fix the wrongly placed replica.

[ https://issues.apache.org/jira/browse/HDFS-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884820#comment-16884820 ] Jinglun commented on HDFS-14631: Hi [~hexiaoqiao], thanks for your great suggestions. The suggestions

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Description: *Problem Description:* In the multi-NameNode scenario, when a SNN uploads a FsImage, it

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Attachment: (was: blockWriiting.png) > Standby NameNode should terminate the FsImage put process

[jira] [Commented] (HDFS-14303) check block directory logic not correct when there is only meta file, print no meaning warn log

[ https://issues.apache.org/jira/browse/HDFS-14303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884717#comment-16884717 ] Ayush Saxena commented on HDFS-14303: - Seems the introduced test, keeps failing in trunk :

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Attachment: largeSendQ.png > Standby NameNode should terminate the FsImage put process as soon as

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Attachment: (was: largeSendQ.png) > Standby NameNode should terminate the FsImage put process as

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Attachment: blockedInWritingSocket.png > Standby NameNode should terminate the FsImage put process as

[jira] [Assigned] (HDFS-11246) FSNameSystem#logAuditEvent should be called outside the read or write locks

[ https://issues.apache.org/jira/browse/HDFS-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] He Xiaoqiao reassigned HDFS-11246: -- Assignee: He Xiaoqiao (was: Kuhu Shukla) > FSNameSystem#logAuditEvent should be called

[jira] [Commented] (HDFS-11246) FSNameSystem#logAuditEvent should be called outside the read or write locks

[ https://issues.apache.org/jira/browse/HDFS-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884848#comment-16884848 ] He Xiaoqiao commented on HDFS-11246: Hi, [~kshukla] I just assign this issue to myself. Please feel

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Description: *Problem Description:* In the multi-NameNode scenario, when a SNN uploads a FsImage, it

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Description: *Problem Description:* In the multi-NameNode scenario, when a SNN uploads a FsImage, it

[jira] [Created] (HDFS-14646) Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image.

Xudong Cao created HDFS-14646: - Summary: Standby NameNode should terminate the FsImage put process as soon as possible if the peer NN is not in the appropriate state to receive an image. Key: HDFS-14646 URL:

[jira] [Commented] (HDDS-1787) NPE thrown while trying to find DN closest to client

[ https://issues.apache.org/jira/browse/HDDS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884825#comment-16884825 ] Sammi Chen commented on HDDS-1787: -- Hi [~swagle], I would like to know how to run the MiniOzoneChaos

[jira] [Updated] (HDFS-14646) Standby NameNode should terminate the FsImage put process immediately if the peer NN is not in the appropriate state to receive an image.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xudong Cao updated HDFS-14646: -- Summary: Standby NameNode should terminate the FsImage put process immediately if the peer NN is not

[jira] [Commented] (HDFS-14631) The DirectoryScanner doesn't fix the wrongly placed replica.

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