[jira] [Updated] (HDFS-15439) Setting dfs.mover.retry.max.attempts to negative value will retry forever.

[ https://issues.apache.org/jira/browse/HDFS-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AMC-team updated HDFS-15439: Attachment: (was: HDFS-15439.000.patch) > Setting dfs.mover.retry.max.attempts to negative value will

[jira] [Updated] (HDFS-15439) Setting dfs.mover.retry.max.attempts to negative value will retry forever.

[ https://issues.apache.org/jira/browse/HDFS-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AMC-team updated HDFS-15439: Attachment: HDFS-15439.000.patch Status: Patch Available (was: Open) > Setting

[jira] [Updated] (HDFS-15438) Setting dfs.disk.balancer.max.disk.errors = 0 will fail the block copy

[ https://issues.apache.org/jira/browse/HDFS-15438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AMC-team updated HDFS-15438: Attachment: (was: HDFS-15438.000.patch) > Setting dfs.disk.balancer.max.disk.errors = 0 will fail the

[jira] [Updated] (HDFS-15438) Setting dfs.disk.balancer.max.disk.errors = 0 will fail the block copy

[ https://issues.apache.org/jira/browse/HDFS-15438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AMC-team updated HDFS-15438: Attachment: HDFS-15438.000.patch Status: Patch Available (was: Open) > Setting

[jira] [Updated] (HDFS-15443) Setting dfs.datanode.max.transfer.threads to a very small value can cause strange failure.

[ https://issues.apache.org/jira/browse/HDFS-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AMC-team updated HDFS-15443: Attachment: HDFS-15443.001.patch Status: Patch Available (was: Open) > Setting

[jira] [Commented] (HDFS-15443) Setting dfs.datanode.max.transfer.threads to a very small value can cause strange failure.

[ https://issues.apache.org/jira/browse/HDFS-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159657#comment-17159657 ] AMC-team commented on HDFS-15443: - [~elgoiri] Sorry about my late feedback. I have uploaded a new patch.

[jira] [Commented] (HDFS-15443) Setting dfs.datanode.max.transfer.threads to a very small value can cause strange failure.

[ https://issues.apache.org/jira/browse/HDFS-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159662#comment-17159662 ] Íñigo Goiri commented on HDFS-15443: +1 on [^HDFS-15443.001.patch]. [~ayushtkn] any objections? >

[jira] [Commented] (HDFS-15443) Setting dfs.datanode.max.transfer.threads to a very small value can cause strange failure.

[ https://issues.apache.org/jira/browse/HDFS-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159671#comment-17159671 ] Ayush Saxena commented on HDFS-15443: - Thanx [~elgoiri] No objections from my side > Setting

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

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

[jira] [Updated] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hongbing Wang updated HDFS-15240: - Attachment: image-2020-07-16-15-56-38-608.png > Erasure Coding: dirty buffer causes

[jira] [Updated] (HDFS-15098) Add SM4 encryption method for HDFS

[ https://issues.apache.org/jira/browse/HDFS-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zZtai updated HDFS-15098: - Attachment: HDFS-15098.009.patch Status: Patch Available (was: Open) > Add SM4 encryption method for

[jira] [Updated] (HDFS-15098) Add SM4 encryption method for HDFS

[ https://issues.apache.org/jira/browse/HDFS-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zZtai updated HDFS-15098: - Status: Open (was: Patch Available) > Add SM4 encryption method for HDFS > -- >

[jira] [Commented] (HDFS-15240) Erasure Coding: dirty buffer causes reconstruction block error

[ https://issues.apache.org/jira/browse/HDFS-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158991#comment-17158991 ] Hongbing Wang commented on HDFS-15240: -- [~marvelrock] We have the same problem. At the same time as

[jira] [Commented] (HDFS-15469) Dynamically configure the size of PacketReceiver#MAX_PACKET_SIZE

[ https://issues.apache.org/jira/browse/HDFS-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159080#comment-17159080 ] jianghua zhu commented on HDFS-15469: - [~hexiaoqiao] , thank you very much. > Dynamically configure

[jira] [Updated] (HDFS-15313) Ensure inodes in active filesytem are not deleted during snapshot delete

[ https://issues.apache.org/jira/browse/HDFS-15313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-15313: - Fix Version/s: 3.1.5 > Ensure inodes in active filesytem are not deleted during snapshot

[jira] [Commented] (HDFS-15098) Add SM4 encryption method for HDFS

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

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159219#comment-17159219 ] Stephen O'Donnell commented on HDFS-14498: -- With HDFS-14498-branch-2.10.004.patch: *

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen O'Donnell updated HDFS-14498: - Attachment: HDFS-14498-branch-2.10.004.patch > LeaseManager can loop forever on the file

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159134#comment-17159134 ] Stephen O'Donnell commented on HDFS-14498: -- Upload a v004 branch-2.10 patch to address the

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

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

[jira] [Updated] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaoqiao He updated HDFS-14498: --- Fix Version/s: 3.1.5 2.10.1 3.2.2 Resolution: Fixed

[jira] [Commented] (HDFS-14498) LeaseManager can loop forever on the file for which create has failed

[ https://issues.apache.org/jira/browse/HDFS-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159331#comment-17159331 ] Xiaoqiao He commented on HDFS-14498: +1. Commit to branch-3.2/branch-3.1/branch-2.10. Thanks

[jira] [Commented] (HDFS-15473) Add listSnapshots command to list all snapshots

[ https://issues.apache.org/jira/browse/HDFS-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159399#comment-17159399 ] Wei-Chiu Chuang commented on HDFS-15473: [~hemanthboyina] can you make an example? Say the

[jira] [Commented] (HDFS-15472) Erasure Coding: Support fallback read when zero copy is not supported

[ https://issues.apache.org/jira/browse/HDFS-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159403#comment-17159403 ] Wei-Chiu Chuang commented on HDFS-15472: thanks for the patch. I think the patch is fine. We

[jira] [Updated] (HDFS-15404) ShellCommandFencer should expose info about source

[ https://issues.apache.org/jira/browse/HDFS-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Liang updated HDFS-15404: -- Attachment: HDFS-15404.005.patch > ShellCommandFencer should expose info about source >

[jira] [Commented] (HDFS-15404) ShellCommandFencer should expose info about source

[ https://issues.apache.org/jira/browse/HDFS-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159408#comment-17159408 ] Chen Liang commented on HDFS-15404: --- Thanks for taking a look [~shv]! In general, I agree that should

[jira] [Updated] (HDFS-15468) Active namenode crashed when no edit recover

[ https://issues.apache.org/jira/browse/HDFS-15468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-15468: --- Component/s: journal-node ha > Active namenode crashed when no edit recover

[jira] [Commented] (HDFS-15404) ShellCommandFencer should expose info about source

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

[jira] [Commented] (HDFS-15025) Applying NVDIMM storage media to HDFS

[ https://issues.apache.org/jira/browse/HDFS-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159614#comment-17159614 ] huangtianhua commented on HDFS-15025: - [~weichiu][~ayushtkn][~brahma] Would you please help to review