[jira] [Updated] (HDDS-1840) Fix TestSecureOzoneContainer

[ https://issues.apache.org/jira/browse/HDDS-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-1840: Resolution: Fixed Fix Version/s: 0.5.0 Target Version/s: (was: 0.5.0)

[jira] [Work logged] (HDDS-1840) Fix TestSecureOzoneContainer

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

[jira] [Work logged] (HDDS-1840) Fix TestSecureOzoneContainer

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

[jira] [Commented] (HDFS-14660) [SBN Read] ObserverNameNode should throw StandbyException for requests not from ObserverProxyProvider

[ https://issues.apache.org/jira/browse/HDFS-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890315#comment-16890315 ] Chao Sun commented on HDFS-14660: - {quote}Now what I think, even if ObserverProxyProvider is set, and the

[jira] [Updated] (HDDS-1707) SCMContainerPlacementRackAware#chooseDatanodes throws not enough datanodes when all nodes(40) are up

[ https://issues.apache.org/jira/browse/HDDS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated HDDS-1707: Target Version/s: 0.5.0 (was: 0.4.1) > SCMContainerPlacementRackAware#chooseDatanodes

[jira] [Commented] (HDFS-14617) Improve fsimage load time by writing sub-sections to the fsimage index

[ https://issues.apache.org/jira/browse/HDFS-14617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890288#comment-16890288 ] Stephen O'Donnell commented on HDFS-14617: -- Thanks for all the comments on this. I hope to get

[jira] [Commented] (HDDS-1816) ContainerStateMachine should limit number of pending apply transactions

[ https://issues.apache.org/jira/browse/HDDS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890287#comment-16890287 ] Lokesh Jain commented on HDDS-1816: --- [~nandakumar131] it is good to have but not a blocker for 0.4.1

[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=16890285#comment-16890285 ] Stephen O'Donnell commented on HDFS-13693: -- I think this performance improvement is a great

[jira] [Work logged] (HDDS-1749) Ozone Client should randomize the list of nodes in pipeline for reads

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

[jira] [Created] (HDDS-1844) Tune the stateMachineDataCache to a reasonable fraction of Datanode Heap

Shashikant Banerjee created HDDS-1844: - Summary: Tune the stateMachineDataCache to a reasonable fraction of Datanode Heap Key: HDDS-1844 URL: https://issues.apache.org/jira/browse/HDDS-1844

[jira] [Created] (HDDS-1843) Close container command should sync the Rocks db before changing to closed state.

Shashikant Banerjee created HDDS-1843: - Summary: Close container command should sync the Rocks db before changing to closed state. Key: HDDS-1843 URL: https://issues.apache.org/jira/browse/HDDS-1843

[jira] [Comment Edited] (HDDS-1753) Datanode unable to find chunk while replication data using ratis.

[ https://issues.apache.org/jira/browse/HDDS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883727#comment-16883727 ] Shashikant Banerjee edited comment on HDDS-1753 at 7/22/19 3:06 PM:

[jira] [Comment Edited] (HDFS-14661) RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist

[ https://issues.apache.org/jira/browse/HDFS-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890236#comment-16890236 ] Ayush Saxena edited comment on HDFS-14661 at 7/22/19 3:04 PM: -- Something

[jira] [Commented] (HDFS-14313) Get hdfs used space from FsDatasetImpl#volumeMap#ReplicaInfo in memory instead of df/du

[ https://issues.apache.org/jira/browse/HDFS-14313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890237#comment-16890237 ] Lisheng Sun commented on HDFS-14313: hi [~linyiqun], could you mind continuing to reiview this patch?

[jira] [Commented] (HDFS-14661) RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist

[ https://issues.apache.org/jira/browse/HDFS-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890236#comment-16890236 ] Ayush Saxena commented on HDFS-14661: - Something similar issue, encountered in HDFS-14331 Ca do

[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=16890228#comment-16890228 ] Lisheng Sun commented on HDFS-13693: hi [~ayushtkn]  If you think this patch no problem, could you

[jira] [Assigned] (HDDS-1834) ozone fs -mkdir -p does not create parent directories in ozonesecure

[ https://issues.apache.org/jira/browse/HDDS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain reassigned HDDS-1834: - Assignee: (was: Lokesh Jain) > ozone fs -mkdir -p does not create parent directories in

[jira] [Updated] (HDFS-10419) Building HDFS on top of new storage layer (HDDS)

[ https://issues.apache.org/jira/browse/HDFS-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang XL updated HDFS-10419: --- Description: In HDFS-7240, Ozone defines storage containers to store both the data and the metadata. The

[jira] [Updated] (HDFS-14579) In refreshNodes, avoid performing a DNS lookup while holding the write lock

[ https://issues.apache.org/jira/browse/HDFS-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-14579: - Resolution: Not A Problem Status: Resolved (was: Patch Available) > In

[jira] [Commented] (HDFS-14637) Namenode may not replicate blocks to meet the policy after enabling upgradeDomain

[ https://issues.apache.org/jira/browse/HDFS-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890199#comment-16890199 ] Stephen O'Donnell commented on HDFS-14637: -- Added a couple of unit tests and hopefully fixed the

[jira] [Updated] (HDFS-14637) Namenode may not replicate blocks to meet the policy after enabling upgradeDomain

[ https://issues.apache.org/jira/browse/HDFS-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-14637: - Attachment: HDFS-14637.002.patch > Namenode may not replicate blocks to meet the policy

[jira] [Updated] (HDFS-14661) RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist

[ https://issues.apache.org/jira/browse/HDFS-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuzq updated HDFS-14661: Attachment: HDFS-14661-HDFS-13891-001.patch > RBF：updateMountTableEntry shouldn't update mountTableEntry if

[jira] [Created] (HDFS-14661) RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist

xuzq created HDFS-14661: --- Summary: RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist Key: HDFS-14661 URL: https://issues.apache.org/jira/browse/HDFS-14661 Project: Hadoop HDFS

[jira] [Commented] (HDFS-14634) the original active namenode should have priority to participate in the election when the zookeeper recovery

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

[jira] [Updated] (HDFS-14634) the original active namenode should have priority to participate in the election when the zookeeper recovery

[ https://issues.apache.org/jira/browse/HDFS-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14634: -- Attachment: (was: HDFS-14634-v2.patch) > the original active namenode should have priority to participate

[jira] [Updated] (HDFS-14634) the original active namenode should have priority to participate in the election when the zookeeper recovery

[ https://issues.apache.org/jira/browse/HDFS-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14634: -- Status: Open (was: Patch Available) > the original active namenode should have priority to participate in

[jira] [Updated] (HDFS-14634) the original active namenode should have priority to participate in the election when the zookeeper recovery

[ https://issues.apache.org/jira/browse/HDFS-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14634: -- Attachment: HDFS-14634.001.patch Status: Patch Available (was: Open) > the original active namenode

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Attachment: HDFS-14616.001.patch > Add the warn log when the volume available space isn't enough >

[jira] [Commented] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890070#comment-16890070 ] liying commented on HDFS-14616: --- Thanks  [~ayushtkn],  I think you are right。It was my mistake for using 

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Attachment: (was: HDFS-14616.001.patch) > Add the warn log when the volume available space isn't enough >

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Attachment: (was: HDFS-14616-v2.patch) > Add the warn log when the volume available space isn't enough >

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Attachment: (was: HDFS-14616-v3.patch) > Add the warn log when the volume available space isn't enough >

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Attachment: (was: HDFS-14616-v1.patch) > Add the warn log when the volume available space isn't enough >

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Attachment: HDFS-14616.001.patch > Add the warn log when the volume available space isn't enough >

[jira] [Updated] (HDFS-14616) Add the warn log when the volume available space isn't enough

[ https://issues.apache.org/jira/browse/HDFS-14616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liying updated HDFS-14616: -- Status: Open (was: Patch Available) > Add the warn log when the volume available space isn't enough >

[jira] [Updated] (HDDS-1751) replication of underReplicated container fails with SCMContainerPlacementRackAware policy

[ https://issues.apache.org/jira/browse/HDDS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1751: -- Target Version/s: 0.5.0 (was: 0.5.0, 0.4.1) > replication of underReplicated container fails with >

[jira] [Commented] (HDDS-1816) ContainerStateMachine should limit number of pending apply transactions

[ https://issues.apache.org/jira/browse/HDDS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890020#comment-16890020 ] Nanda kumar commented on HDDS-1816: --- [~ljain], do we need this for 0.4.1 release? >

[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=16890005#comment-16890005 ] qiang Liu commented on HDFS-14303: -- [~ayushtkn] after doing some debug, finally figure it out. test

[jira] [Updated] (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:all-tabpanel ] qiang Liu updated HDFS-14303: - Attachment: HDFS-14303-trunk.018.patch > check block directory logic not correct when there is only meta

[jira] [Commented] (HDFS-14595) HDFS-11848 breaks API compatibility

[ https://issues.apache.org/jira/browse/HDFS-14595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889987#comment-16889987 ] Ayush Saxena commented on HDFS-14595: - I guess to avoid the incompatibility, we just need to ensure

[jira] [Commented] (HDFS-14647) NPE during secure namenode startup

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

[jira] [Updated] (HDDS-1798) Propagate failure in writeStateMachineData to Ratis

[ https://issues.apache.org/jira/browse/HDDS-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supratim Deka updated HDDS-1798: Status: Patch Available (was: Open) > Propagate failure in writeStateMachineData to Ratis >

[jira] [Work logged] (HDDS-1798) Propagate failure in writeStateMachineData to Ratis

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

<    1   2