[jira] [Commented] (HDFS-14809) Make a new BlockReader for hdfs client lib

[ https://issues.apache.org/jira/browse/HDFS-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925623#comment-16925623 ] KenCao commented on HDFS-14809: --- I have made an impletation. There is another impletation called

[jira] [Commented] (HDFS-14378) Simplify the design of multiple NN and both logic of edit log roll and checkpoint

[ https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925622#comment-16925622 ] star commented on HDFS-14378: - Thanks [~jojochuang] for reviewing and advise. Section 7.6 of HDFS-1073

[jira] [Updated] (HDFS-14809) Make a new BlockReader for hdfs client lib

[ https://issues.apache.org/jira/browse/HDFS-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] KenCao updated HDFS-14809: -- Attachment: HADOOP-14809 > Make a new BlockReader for hdfs client lib >

[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=16925598#comment-16925598 ] Hadoop QA commented on HDFS-14303: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-14835) RBF: Secured Router should not run when it can't initialize DelegationTokenSecretManager

[ https://issues.apache.org/jira/browse/HDFS-14835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takanobu Asanuma updated HDFS-14835: Status: Patch Available (was: Open) > RBF: Secured Router should not run when it can't

[jira] [Work logged] (HDDS-2076) Read fails because the block cannot be located in the container

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

[jira] [Work logged] (HDDS-2076) Read fails because the block cannot be located in the container

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

[jira] [Work logged] (HDDS-2057) Incorrect Default OM Port in Ozone FS URI Error Message

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

[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=16925579#comment-16925579 ] He Xiaoqiao commented on HDFS-14303: [^HDFS-14303-branch-3.2.addendum.03.patch] upload addendum patch

[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 ] He Xiaoqiao updated HDFS-14303: --- Attachment: HDFS-14303-branch-3.2.addendum.03.patch > check block directory logic not correct when

[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=16925535#comment-16925535 ] Ayush Saxena commented on HDFS-14303: - No, it doesn’t > check block directory logic not correct

[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=16925531#comment-16925531 ] He Xiaoqiao commented on HDFS-14303: Hi [~ayushtkn], [^HDFS-14303-addendum-02.patch] only apply to

[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=16925525#comment-16925525 ] Ayush Saxena commented on HDFS-14303: - Guess we would require patch for branch-3.2 and 3.1 branch >

[jira] [Commented] (HDFS-13157) Do Not Remove Blocks Sequentially During Decommission

[ https://issues.apache.org/jira/browse/HDFS-13157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925523#comment-16925523 ] Stephen O'Donnell commented on HDFS-13157: -- > How is it handled, iterating through each

[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=16925517#comment-16925517 ] He Xiaoqiao commented on HDFS-14303: upload new patch file with no changes compare to

[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 ] He Xiaoqiao updated HDFS-14303: --- Attachment: HDFS-14303-branch-2.addendum.02.patch > check block directory logic not correct when

[jira] [Work logged] (HDDS-2076) Read fails because the block cannot be located in the container

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

[jira] [Work logged] (HDDS-2076) Read fails because the block cannot be located in the container

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

[jira] [Created] (HDFS-14835) RBF: Secured Router should not run when it can't initialize DelegationTokenSecretManager

Takanobu Asanuma created HDFS-14835: --- Summary: RBF: Secured Router should not run when it can't initialize DelegationTokenSecretManager Key: HDFS-14835 URL: https://issues.apache.org/jira/browse/HDFS-14835

[jira] [Commented] (HDFS-13762) Support non-volatile storage class memory(SCM) in HDFS cache directives

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

[jira] [Updated] (HDFS-13762) Support non-volatile storage class memory(SCM) in HDFS cache directives

[ https://issues.apache.org/jira/browse/HDFS-13762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feilong He updated HDFS-13762: -- Attachment: HDFS_Persistent_Memory_Cache_Perf_Results.pdf > Support non-volatile storage class

[jira] [Updated] (HDFS-13762) Support non-volatile storage class memory(SCM) in HDFS cache directives

[ https://issues.apache.org/jira/browse/HDFS-13762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feilong He updated HDFS-13762: -- Attachment: (was: HDFS_Persistent_Memory_Cache_Perf_Results.pdf) > Support non-volatile storage

[jira] [Commented] (HDFS-14834) in some particular situation, datanode will always in DECOMMISSION_INPROGRESS state

[ https://issues.apache.org/jira/browse/HDFS-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925447#comment-16925447 ] janick.wu commented on HDFS-14834: -- [~ayushtkn] yes, it can fix this bug, thxs for your attention > in

[jira] [Work logged] (HDDS-2048) State check during container state transition in datanode should be lock protected

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

[jira] [Commented] (HDDS-2048) State check during container state transition in datanode should be lock protected

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

[jira] [Comment Edited] (HDFS-14811) RBF: TestRouterRpc#testErasureCoding is flaky

[ https://issues.apache.org/jira/browse/HDFS-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925202#comment-16925202 ] Chen Zhang edited comment on HDFS-14811 at 9/9/19 7:27 AM: --- Hi [~ayushtkn],

[jira] [Resolved] (HDDS-2094) TestOzoneManagerRatisServer is failing

[ https://issues.apache.org/jira/browse/HDDS-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved HDDS-2094. - Resolution: Duplicate > TestOzoneManagerRatisServer is failing >

[jira] [Updated] (HDDS-2053) Fix TestOzoneManagerRatisServer failure

[ https://issues.apache.org/jira/browse/HDDS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated HDDS-2053: Description: {{TestOzoneManagerRatisServer}} is failing on trunk with the following error

[jira] [Updated] (HDDS-2053) Fix TestOzoneManagerRatisServer failure

[ https://issues.apache.org/jira/browse/HDDS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated HDDS-2053: Component/s: test > Fix TestOzoneManagerRatisServer failure >

[jira] [Updated] (HDDS-2053) Fix TestOzoneManagerRatisServer failure

[ https://issues.apache.org/jira/browse/HDDS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated HDDS-2053: Issue Type: Bug (was: Test) > Fix TestOzoneManagerRatisServer failure >

[jira] [Work logged] (HDDS-2007) Make ozone fs shell command work with OM HA service ids

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

[jira] [Work logged] (HDDS-2007) Make ozone fs shell command work with OM HA service ids

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

[jira] [Assigned] (HDDS-1564) Ozone multi-raft support

[ https://issues.apache.org/jira/browse/HDDS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Cheng reassigned HDDS-1564: -- Assignee: Li Cheng (was: Siddharth Wagle) > Ozone multi-raft support > > >

[jira] [Comment Edited] (HDFS-14646) Standby NameNode should not upload fsimage to an inappropriate NameNode.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925408#comment-16925408 ] Xudong Cao edited comment on HDFS-14646 at 9/9/19 6:46 AM: --- Thanks [~csun] 

[jira] [Comment Edited] (HDFS-14646) Standby NameNode should not upload fsimage to an inappropriate NameNode.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925408#comment-16925408 ] Xudong Cao edited comment on HDFS-14646 at 9/9/19 6:44 AM: --- Thanks [~csun] 

[jira] [Updated] (HDFS-14646) Standby NameNode should not upload fsimage to an inappropriate NameNode.

[ 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 not upload fsimage to an inappropriate NameNode.

[ 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-14646) Standby NameNode should not upload fsimage to an inappropriate NameNode.

[ https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925408#comment-16925408 ] Xudong Cao commented on HDFS-14646: --- Thanks [~csun]  very mush for reviewing, I have corrected all the

[jira] [Commented] (HDFS-14646) Standby NameNode should not upload fsimage to an inappropriate NameNode.

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

[jira] [Commented] (HDDS-1868) Ozone pipelines should be marked as ready only after the leader election is complete

[ https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925401#comment-16925401 ] Lokesh Jain commented on HDDS-1868: --- [~swagle] In the patch below condition would only be true for the

[jira] [Work logged] (HDDS-2048) State check during container state transition in datanode should be lock protected

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

<    1   2