[jira] [Updated] (HDFS-4903) Print trash configuration and trash emptier state in namenode log

[ https://issues.apache.org/jira/browse/HDFS-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4903: -- Resolution: Fixed Fix Version/s: 1.3.0 Hadoop Flags: Reviewed Status:

[jira] [Commented] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered

[ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710892#comment-13710892 ] Hadoop QA commented on HDFS-5002: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered

[ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710903#comment-13710903 ] Kousuke Saruta commented on HDFS-5002: -- No new tests added because this only removed a

[jira] [Commented] (HDFS-4657) Limit the number of blocks logged by the NN after a block report to a configurable value.

[ https://issues.apache.org/jira/browse/HDFS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710954#comment-13710954 ] Hudson commented on HDFS-4657: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #273 (See

[jira] [Commented] (HDFS-4998) TestUnderReplicatedBlocks fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710951#comment-13710951 ] Hudson commented on HDFS-4998: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #273 (See

[jira] [Commented] (HDFS-4992) Make balancer's thread count configurable

[ https://issues.apache.org/jira/browse/HDFS-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710950#comment-13710950 ] Hudson commented on HDFS-4992: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #273 (See

[jira] [Commented] (HDFS-4998) TestUnderReplicatedBlocks fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711034#comment-13711034 ] Hudson commented on HDFS-4998: -- SUCCESS: Integrated in Hadoop-Hdfs-0.23-Build #671 (See

[jira] [Commented] (HDFS-4992) Make balancer's thread count configurable

[ https://issues.apache.org/jira/browse/HDFS-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711057#comment-13711057 ] Hudson commented on HDFS-4992: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1463 (See

[jira] [Commented] (HDFS-4657) Limit the number of blocks logged by the NN after a block report to a configurable value.

[ https://issues.apache.org/jira/browse/HDFS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711061#comment-13711061 ] Hudson commented on HDFS-4657: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1463 (See

[jira] [Commented] (HDFS-4998) TestUnderReplicatedBlocks fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711058#comment-13711058 ] Hudson commented on HDFS-4998: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1463 (See

[jira] [Updated] (HDFS-4510) Cover classes ClusterJspHelper/NamenodeJspHelper with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Y updated HDFS-4510: --- Attachment: HDFS-4510-trunk--N27.patch fixed merge conflict Cover classes

[jira] [Commented] (HDFS-4998) TestUnderReplicatedBlocks fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711105#comment-13711105 ] Hudson commented on HDFS-4998: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1490 (See

[jira] [Commented] (HDFS-4992) Make balancer's thread count configurable

[ https://issues.apache.org/jira/browse/HDFS-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711104#comment-13711104 ] Hudson commented on HDFS-4992: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1490 (See

[jira] [Commented] (HDFS-4657) Limit the number of blocks logged by the NN after a block report to a configurable value.

[ https://issues.apache.org/jira/browse/HDFS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711108#comment-13711108 ] Hudson commented on HDFS-4657: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1490 (See

[jira] [Updated] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Y updated HDFS-4517: --- Attachment: HDFS-4517-branch-2--N3.patch fixed merge conflict for branch-2 Cover class

[jira] [Commented] (HDFS-4602) TestBookKeeperHACheckpoints fails

[ https://issues.apache.org/jira/browse/HDFS-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711174#comment-13711174 ] Uma Maheswara Rao G commented on HDFS-4602: --- Let me take a look on it. Thanks

[jira] [Commented] (HDFS-4510) Cover classes ClusterJspHelper/NamenodeJspHelper with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711203#comment-13711203 ] Hadoop QA commented on HDFS-4510: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Component/s: namenode Add additional JMX bean for NameNode status data

[jira] [Created] (HDFS-5004) Add additional JMX bean for NameNode status data

Trevor Lorimer created HDFS-5004: Summary: Add additional JMX bean for NameNode status data Key: HDFS-5004 URL: https://issues.apache.org/jira/browse/HDFS-5004 Project: Hadoop HDFS Issue

[jira] [Commented] (HDFS-4517) Cover class RemoteBlockReader with unit tests

[ https://issues.apache.org/jira/browse/HDFS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711265#comment-13711265 ] Hadoop QA commented on HDFS-4517: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-3752) BOOTSTRAPSTANDBY for new Standby node will not work just after saveNameSpace at ANN in case of BKJM

[ https://issues.apache.org/jira/browse/HDFS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711317#comment-13711317 ] kumar y commented on HDFS-3752: --- I havent seen any updates for a while. can someone please

[jira] [Resolved] (HDFS-4672) Support tiered storage policies

[ https://issues.apache.org/jira/browse/HDFS-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HDFS-4672. -- Resolution: Later HDFS-2832 and new subtasks have picked up some ideas from here, we might

[jira] [Resolved] (HDFS-3994) misleading comment in CommonConfigurationKeysPublic

[ https://issues.apache.org/jira/browse/HDFS-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HDFS-3994. Resolution: Won't Fix I looked at this again, and I think the intention is just

[jira] [Commented] (HDFS-2832) Enable support for heterogeneous storages in HDFS

[ https://issues.apache.org/jira/browse/HDFS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711356#comment-13711356 ] Bikas Saha commented on HDFS-2832: -- Is there an overall design document that one can

[jira] [Commented] (HDFS-2832) Enable support for heterogeneous storages in HDFS

[ https://issues.apache.org/jira/browse/HDFS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711362#comment-13711362 ] Andrew Purtell commented on HDFS-2832: -- [~sanjay.radia] bq. Your recent tweet about

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Attachment: HDFS-5004.diff Add additional JMX bean for NameNode status data

[jira] [Updated] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated HDFS-5004: - Status: Patch Available (was: Open) Add additional JMX bean for NameNode status data

[jira] [Updated] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Fang updated HDFS-5001: -- Summary: Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1)

[jira] [Commented] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711420#comment-13711420 ] Hadoop QA commented on HDFS-5004: - {color:red}-1 overall{color}. Here are the results of

[jira] [Created] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

Jing Zhao created HDFS-5005: --- Summary: Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol Key: HDFS-5005 URL: https://issues.apache.org/jira/browse/HDFS-5005 Project: Hadoop

[jira] [Updated] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5005: Attachment: HDFS-5005.001.patch The simple patch only does the rename. Move

[jira] [Updated] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5005: Status: Patch Available (was: Open) Move SnapshotException and SnapshotAccessControlException to

[jira] [Commented] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered

[ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711554#comment-13711554 ] Jing Zhao commented on HDFS-5002: - Hi Kousuke, Thanks for the patch! Looks like

[jira] [Updated] (HDFS-5003) Branch-1-Win TestNNThroughputBenchmark failed

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Fang updated HDFS-5003: -- Attachment: HADOOP-9739.1.trunk.patch Branch-1-Win TestNNThroughputBenchmark failed

[jira] [Updated] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Fang updated HDFS-5003: -- Summary: TestNNThroughputBenchmark failed caused by existing directories (was: Branch-1-Win

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711600#comment-13711600 ] Xi Fang commented on HDFS-5003: --- Thanks Chris. A patch for trunk was attached.

[jira] [Commented] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711613#comment-13711613 ] Hadoop QA commented on HDFS-5004: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-5004) Add additional JMX bean for NameNode status data

[ https://issues.apache.org/jira/browse/HDFS-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711615#comment-13711615 ] Konstantin Boudnik commented on HDFS-5004: -- Looks like JavaDoc is wrong which

[jira] [Commented] (HDFS-4943) WebHdfsFileSystem does not work when original file path has encoded chars

[ https://issues.apache.org/jira/browse/HDFS-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711682#comment-13711682 ] Kihwal Lee commented on HDFS-4943: -- The 0.23 patch looks good. I will commit it shortly.

[jira] [Updated] (HDFS-4943) WebHdfsFileSystem does not work when original file path has encoded chars

[ https://issues.apache.org/jira/browse/HDFS-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-4943: - Fix Version/s: 0.23.10 WebHdfsFileSystem does not work when original file path has encoded chars

[jira] [Updated] (HDFS-4943) WebHdfsFileSystem does not work when original file path has encoded chars

[ https://issues.apache.org/jira/browse/HDFS-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-4943: - Affects Version/s: 0.23.10 WebHdfsFileSystem does not work when original file path has encoded chars

[jira] [Commented] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711693#comment-13711693 ] Hadoop QA commented on HDFS-5005: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: HDFS-4979.3.patch Here is an updated patch. I had a chat with [~jingzhao], who

[jira] [Updated] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Fang updated HDFS-5003: -- Fix Version/s: 2.1.0-beta 1-win 3.0.0 Status: Patch Available

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: (was: HDFS-4979.3.patch) Implement retry cache on the namenode

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: HDFS-4979.3.patch Implement retry cache on the namenode

[jira] [Commented] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711729#comment-13711729 ] Sanjay Radia commented on HDFS-5005: +1 Move SnapshotException and

[jira] [Commented] (HDFS-2832) Enable support for heterogeneous storages in HDFS

[ https://issues.apache.org/jira/browse/HDFS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711771#comment-13711771 ] Arpit Agarwal commented on HDFS-2832: - [~bikassaha] We'll post a design doc by next

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711815#comment-13711815 ] Hadoop QA commented on HDFS-5003: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711827#comment-13711827 ] Hadoop QA commented on HDFS-4979: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5005: Resolution: Fixed Fix Version/s: 2.1.0-beta Hadoop Flags: Reviewed Status: Resolved

[jira] [Commented] (HDFS-5005) Move SnapshotException and SnapshotAccessControlException to o.a.h.hdfs.protocol

[ https://issues.apache.org/jira/browse/HDFS-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711857#comment-13711857 ] Hudson commented on HDFS-5005: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4107 (See

[jira] [Updated] (HDFS-5006) Provide a link to symlink target in the web UI

[ https://issues.apache.org/jira/browse/HDFS-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Chu updated HDFS-5006: -- Attachment: screenshot2.png screenshot1.png Provide a link to symlink target in

[jira] [Created] (HDFS-5006) Provide a link to symlink target in the web UI

Stephen Chu created HDFS-5006: - Summary: Provide a link to symlink target in the web UI Key: HDFS-5006 URL: https://issues.apache.org/jira/browse/HDFS-5006 Project: Hadoop HDFS Issue Type:

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: HDFS-4979.4.patch The failures are due to startFileInternal calling delete. This

[jira] [Commented] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered

[ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711893#comment-13711893 ] Kousuke Saruta commented on HDFS-5002: -- Hi Jing, Thank you for your comment! the

[jira] [Created] (HDFS-5007) the property key dfs.http.port and dfs.https.port are hard corded

Kousuke Saruta created HDFS-5007: Summary: the property key dfs.http.port and dfs.https.port are hard corded Key: HDFS-5007 URL: https://issues.apache.org/jira/browse/HDFS-5007 Project: Hadoop HDFS

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711961#comment-13711961 ] Hadoop QA commented on HDFS-4979: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5003: Target Version/s: 3.0.0, 1-win, 2.1.0-beta, 1.2.1 (was: 3.0.0, 1-win, 2.1.0-beta) Affects

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13711977#comment-13711977 ] Hudson commented on HDFS-5003: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4108 (See

[jira] [Updated] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-5001: -- Assignee: Xi Fang Branch-1-Win TestAzureBlockPlacementPolicy and

[jira] [Updated] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5003: Target Version/s: 3.0.0, 1-win, 2.1.0-beta, 1.3.0 (was: 3.0.0, 1-win, 2.1.0-beta, 1.2.1)

[jira] [Updated] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5003: Resolution: Fixed Status: Resolved (was: Patch Available) Thank you for the contribution,

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Attachment: HDFS-4979.5.patch Updated patch to fix failures and complete retry cache for all

[jira] [Commented] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712019#comment-13712019 ] Chuan Liu commented on HDFS-5001: - +1 on the NetworkTopology change. Resetting

[jira] [Work started] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-5001 started by Xi Fang. Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect

[jira] [Commented] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712021#comment-13712021 ] Xi Fang commented on HDFS-5001: --- Thanks Chuan! Branch-1-Win

[jira] [Commented] (HDFS-5003) TestNNThroughputBenchmark failed caused by existing directories

[ https://issues.apache.org/jira/browse/HDFS-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712020#comment-13712020 ] Xi Fang commented on HDFS-5003: --- Thanks Chris! TestNNThroughputBenchmark

[jira] [Commented] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered

[ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712024#comment-13712024 ] Jing Zhao commented on HDFS-5002: - bq. 1. Removing older field DFS_HTTPS_PORT_KEY. bq. 2.

[jira] [Updated] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5001: Component/s: namenode Target Version/s: 1-win Hadoop Flags: Reviewed +1 for the

[jira] [Updated] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-5001: I committed this to branch-1-win. Thank you for your patch, Xi. Branch-1-Win

[jira] [Resolved] (HDFS-5001) Branch-1-Win TestAzureBlockPlacementPolicy and TestReplicationPolicyWithNodeGroup failed caused by 1) old APIs and 2) incorrect value of depthOfAllLeaves

[ https://issues.apache.org/jira/browse/HDFS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HDFS-5001. - Resolution: Fixed Branch-1-Win TestAzureBlockPlacementPolicy and

[jira] [Commented] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered

[ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712032#comment-13712032 ] Kousuke Saruta commented on HDFS-5002: -- Sure. I also create a jira HDFS-5007 to

[jira] [Updated] (HDFS-5007) the property key dfs.http.port and dfs.https.port are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5007: - Status: Patch Available (was: Open) the property key dfs.http.port and dfs.https.port are

[jira] [Updated] (HDFS-5007) the property key dfs.http.port and dfs.https.port are hard corded

[ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5007: - Attachment: HDFS-5007.patch I found not only dfs.http.port and dfs.https.port property keys but