[jira] [Commented] (HDFS-7420) Delegate permission checks to FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221934#comment-14221934 ] Hudson commented on HDFS-7420: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #751 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/751/]) HDFS-7420. Delegate permission checks to FSDirectory. Contributed by Haohui Mai. (wheat9: rev 23dacb38924e3ed6a456b1c526e71e13e3c8f30d) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSPermissionChecker.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java Delegate permission checks to FSDirectory - Key: HDFS-7420 URL: https://issues.apache.org/jira/browse/HDFS-7420 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Haohui Mai Assignee: Haohui Mai Fix For: 2.7.0 Attachments: HDFS-7420.000.patch, HDFS-7420.001.patch Many permission checks are in fact related to {{FSDirectory}} instead of {{FSNameSystem}}. It would be nice to move them to {{FSDirectory}} to reduce the effort of moving other functions from {{FSNameSystem}} to {{FSDirectory}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7420) Delegate permission checks to FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221927#comment-14221927 ] Hudson commented on HDFS-7420: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/13/]) HDFS-7420. Delegate permission checks to FSDirectory. Contributed by Haohui Mai. (wheat9: rev 23dacb38924e3ed6a456b1c526e71e13e3c8f30d) * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSPermissionChecker.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt Delegate permission checks to FSDirectory - Key: HDFS-7420 URL: https://issues.apache.org/jira/browse/HDFS-7420 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Haohui Mai Assignee: Haohui Mai Fix For: 2.7.0 Attachments: HDFS-7420.000.patch, HDFS-7420.001.patch Many permission checks are in fact related to {{FSDirectory}} instead of {{FSNameSystem}}. It would be nice to move them to {{FSDirectory}} to reduce the effort of moving other functions from {{FSNameSystem}} to {{FSDirectory}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221936#comment-14221936 ] Hudson commented on HDFS-7425: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #751 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/751/]) HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth. (cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.6.0 Reporter: Chris Nauroth Assignee: Chris Nauroth Priority: Minor Fix For: 2.6.1 Attachments: HDFS-7425-branch-2.1.patch The NameNode uses 2 separate Log4J appenders for tracking state changes. The appenders are named org.apache.hadoop.hdfs.StateChange and BlockStateChange. The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately. In branch-2, there is some block state change logging that incorrectly goes to the org.apache.hadoop.hdfs.StateChange appender though. The bug is not present in trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7331) Add Datanode network counts to datanode jmx page
[ https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221932#comment-14221932 ] Hudson commented on HDFS-7331: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #751 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/751/]) HDFS-7331. Add Datanode network counts to datanode jmx page. Contributed by Charles Lamb. (atm: rev 2d4f3e567e4bb8068c028de12df118a4f3fa6343) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeMetrics.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNodeMXBean.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java Add Datanode network counts to datanode jmx page Key: HDFS-7331 URL: https://issues.apache.org/jira/browse/HDFS-7331 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Charles Lamb Assignee: Charles Lamb Priority: Minor Fix For: 2.7.0 Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch, HDFS-7331.003.patch, HDFS-7331.004.patch Add per-datanode counts to the datanode jmx page. For example, networkErrors could be exposed like this: {noformat} }, { ... DatanodeNetworkCounts : {\dn1\:{\networkErrors\:1}}, ... NamenodeAddresses : {\localhost\:\BP-1103235125-127.0.0.1-1415057084497\}, VolumeInfo : {\/tmp/hadoop-cwl/dfs/data/current\:{\freeSpace\:3092725760,\usedSpace\:28672,\reservedSpace\:0}}, ClusterId : CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e }, { {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7331) Add Datanode network counts to datanode jmx page
[ https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221925#comment-14221925 ] Hudson commented on HDFS-7331: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/13/]) HDFS-7331. Add Datanode network counts to datanode jmx page. Contributed by Charles Lamb. (atm: rev 2d4f3e567e4bb8068c028de12df118a4f3fa6343) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeMetrics.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNodeMXBean.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt Add Datanode network counts to datanode jmx page Key: HDFS-7331 URL: https://issues.apache.org/jira/browse/HDFS-7331 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Charles Lamb Assignee: Charles Lamb Priority: Minor Fix For: 2.7.0 Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch, HDFS-7331.003.patch, HDFS-7331.004.patch Add per-datanode counts to the datanode jmx page. For example, networkErrors could be exposed like this: {noformat} }, { ... DatanodeNetworkCounts : {\dn1\:{\networkErrors\:1}}, ... NamenodeAddresses : {\localhost\:\BP-1103235125-127.0.0.1-1415057084497\}, VolumeInfo : {\/tmp/hadoop-cwl/dfs/data/current\:{\freeSpace\:3092725760,\usedSpace\:28672,\reservedSpace\:0}}, ClusterId : CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e }, { {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221929#comment-14221929 ] Hudson commented on HDFS-7425: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/13/]) HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth. (cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.6.0 Reporter: Chris Nauroth Assignee: Chris Nauroth Priority: Minor Fix For: 2.6.1 Attachments: HDFS-7425-branch-2.1.patch The NameNode uses 2 separate Log4J appenders for tracking state changes. The appenders are named org.apache.hadoop.hdfs.StateChange and BlockStateChange. The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately. In branch-2, there is some block state change logging that incorrectly goes to the org.apache.hadoop.hdfs.StateChange appender though. The bug is not present in trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7420) Delegate permission checks to FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221959#comment-14221959 ] Hudson commented on HDFS-7420: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1941 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1941/]) HDFS-7420. Delegate permission checks to FSDirectory. Contributed by Haohui Mai. (wheat9: rev 23dacb38924e3ed6a456b1c526e71e13e3c8f30d) * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSPermissionChecker.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java Delegate permission checks to FSDirectory - Key: HDFS-7420 URL: https://issues.apache.org/jira/browse/HDFS-7420 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Haohui Mai Assignee: Haohui Mai Fix For: 2.7.0 Attachments: HDFS-7420.000.patch, HDFS-7420.001.patch Many permission checks are in fact related to {{FSDirectory}} instead of {{FSNameSystem}}. It would be nice to move them to {{FSDirectory}} to reduce the effort of moving other functions from {{FSNameSystem}} to {{FSDirectory}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221961#comment-14221961 ] Hudson commented on HDFS-7425: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1941 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1941/]) HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth. (cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.6.0 Reporter: Chris Nauroth Assignee: Chris Nauroth Priority: Minor Fix For: 2.6.1 Attachments: HDFS-7425-branch-2.1.patch The NameNode uses 2 separate Log4J appenders for tracking state changes. The appenders are named org.apache.hadoop.hdfs.StateChange and BlockStateChange. The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately. In branch-2, there is some block state change logging that incorrectly goes to the org.apache.hadoop.hdfs.StateChange appender though. The bug is not present in trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7331) Add Datanode network counts to datanode jmx page
[ https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221957#comment-14221957 ] Hudson commented on HDFS-7331: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1941 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1941/]) HDFS-7331. Add Datanode network counts to datanode jmx page. Contributed by Charles Lamb. (atm: rev 2d4f3e567e4bb8068c028de12df118a4f3fa6343) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeMetrics.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNodeMXBean.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java Add Datanode network counts to datanode jmx page Key: HDFS-7331 URL: https://issues.apache.org/jira/browse/HDFS-7331 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Charles Lamb Assignee: Charles Lamb Priority: Minor Fix For: 2.7.0 Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch, HDFS-7331.003.patch, HDFS-7331.004.patch Add per-datanode counts to the datanode jmx page. For example, networkErrors could be exposed like this: {noformat} }, { ... DatanodeNetworkCounts : {\dn1\:{\networkErrors\:1}}, ... NamenodeAddresses : {\localhost\:\BP-1103235125-127.0.0.1-1415057084497\}, VolumeInfo : {\/tmp/hadoop-cwl/dfs/data/current\:{\freeSpace\:3092725760,\usedSpace\:28672,\reservedSpace\:0}}, ClusterId : CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e }, { {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7420) Delegate permission checks to FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221966#comment-14221966 ] Hudson commented on HDFS-7420: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/13/]) HDFS-7420. Delegate permission checks to FSDirectory. Contributed by Haohui Mai. (wheat9: rev 23dacb38924e3ed6a456b1c526e71e13e3c8f30d) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSPermissionChecker.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java Delegate permission checks to FSDirectory - Key: HDFS-7420 URL: https://issues.apache.org/jira/browse/HDFS-7420 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Haohui Mai Assignee: Haohui Mai Fix For: 2.7.0 Attachments: HDFS-7420.000.patch, HDFS-7420.001.patch Many permission checks are in fact related to {{FSDirectory}} instead of {{FSNameSystem}}. It would be nice to move them to {{FSDirectory}} to reduce the effort of moving other functions from {{FSNameSystem}} to {{FSDirectory}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7331) Add Datanode network counts to datanode jmx page
[ https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221964#comment-14221964 ] Hudson commented on HDFS-7331: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/13/]) HDFS-7331. Add Datanode network counts to datanode jmx page. Contributed by Charles Lamb. (atm: rev 2d4f3e567e4bb8068c028de12df118a4f3fa6343) * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeMetrics.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNodeMXBean.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java Add Datanode network counts to datanode jmx page Key: HDFS-7331 URL: https://issues.apache.org/jira/browse/HDFS-7331 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Charles Lamb Assignee: Charles Lamb Priority: Minor Fix For: 2.7.0 Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch, HDFS-7331.003.patch, HDFS-7331.004.patch Add per-datanode counts to the datanode jmx page. For example, networkErrors could be exposed like this: {noformat} }, { ... DatanodeNetworkCounts : {\dn1\:{\networkErrors\:1}}, ... NamenodeAddresses : {\localhost\:\BP-1103235125-127.0.0.1-1415057084497\}, VolumeInfo : {\/tmp/hadoop-cwl/dfs/data/current\:{\freeSpace\:3092725760,\usedSpace\:28672,\reservedSpace\:0}}, ClusterId : CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e }, { {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221968#comment-14221968 ] Hudson commented on HDFS-7425: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/13/]) HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth. (cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.6.0 Reporter: Chris Nauroth Assignee: Chris Nauroth Priority: Minor Fix For: 2.6.1 Attachments: HDFS-7425-branch-2.1.patch The NameNode uses 2 separate Log4J appenders for tracking state changes. The appenders are named org.apache.hadoop.hdfs.StateChange and BlockStateChange. The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately. In branch-2, there is some block state change logging that incorrectly goes to the org.apache.hadoop.hdfs.StateChange appender though. The bug is not present in trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7420) Delegate permission checks to FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221996#comment-14221996 ] Hudson commented on HDFS-7420: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/13/]) HDFS-7420. Delegate permission checks to FSDirectory. Contributed by Haohui Mai. (wheat9: rev 23dacb38924e3ed6a456b1c526e71e13e3c8f30d) * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSPermissionChecker.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java Delegate permission checks to FSDirectory - Key: HDFS-7420 URL: https://issues.apache.org/jira/browse/HDFS-7420 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Haohui Mai Assignee: Haohui Mai Fix For: 2.7.0 Attachments: HDFS-7420.000.patch, HDFS-7420.001.patch Many permission checks are in fact related to {{FSDirectory}} instead of {{FSNameSystem}}. It would be nice to move them to {{FSDirectory}} to reduce the effort of moving other functions from {{FSNameSystem}} to {{FSDirectory}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221998#comment-14221998 ] Hudson commented on HDFS-7425: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/13/]) HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth. (cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.6.0 Reporter: Chris Nauroth Assignee: Chris Nauroth Priority: Minor Fix For: 2.6.1 Attachments: HDFS-7425-branch-2.1.patch The NameNode uses 2 separate Log4J appenders for tracking state changes. The appenders are named org.apache.hadoop.hdfs.StateChange and BlockStateChange. The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately. In branch-2, there is some block state change logging that incorrectly goes to the org.apache.hadoop.hdfs.StateChange appender though. The bug is not present in trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7331) Add Datanode network counts to datanode jmx page
[ https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221994#comment-14221994 ] Hudson commented on HDFS-7331: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #13 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/13/]) HDFS-7331. Add Datanode network counts to datanode jmx page. Contributed by Charles Lamb. (atm: rev 2d4f3e567e4bb8068c028de12df118a4f3fa6343) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNodeMXBean.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeMetrics.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java Add Datanode network counts to datanode jmx page Key: HDFS-7331 URL: https://issues.apache.org/jira/browse/HDFS-7331 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Charles Lamb Assignee: Charles Lamb Priority: Minor Fix For: 2.7.0 Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch, HDFS-7331.003.patch, HDFS-7331.004.patch Add per-datanode counts to the datanode jmx page. For example, networkErrors could be exposed like this: {noformat} }, { ... DatanodeNetworkCounts : {\dn1\:{\networkErrors\:1}}, ... NamenodeAddresses : {\localhost\:\BP-1103235125-127.0.0.1-1415057084497\}, VolumeInfo : {\/tmp/hadoop-cwl/dfs/data/current\:{\freeSpace\:3092725760,\usedSpace\:28672,\reservedSpace\:0}}, ClusterId : CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e }, { {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
[ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222005#comment-14222005 ] Hudson commented on HDFS-7425: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1965 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1965/]) HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth. (cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt NameNode block deletion logging uses incorrect appender. Key: HDFS-7425 URL: https://issues.apache.org/jira/browse/HDFS-7425 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.6.0 Reporter: Chris Nauroth Assignee: Chris Nauroth Priority: Minor Fix For: 2.6.1 Attachments: HDFS-7425-branch-2.1.patch The NameNode uses 2 separate Log4J appenders for tracking state changes. The appenders are named org.apache.hadoop.hdfs.StateChange and BlockStateChange. The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately. In branch-2, there is some block state change logging that incorrectly goes to the org.apache.hadoop.hdfs.StateChange appender though. The bug is not present in trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7420) Delegate permission checks to FSDirectory
[ https://issues.apache.org/jira/browse/HDFS-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222003#comment-14222003 ] Hudson commented on HDFS-7420: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1965 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1965/]) HDFS-7420. Delegate permission checks to FSDirectory. Contributed by Haohui Mai. (wheat9: rev 23dacb38924e3ed6a456b1c526e71e13e3c8f30d) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSPermissionChecker.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java Delegate permission checks to FSDirectory - Key: HDFS-7420 URL: https://issues.apache.org/jira/browse/HDFS-7420 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Haohui Mai Assignee: Haohui Mai Fix For: 2.7.0 Attachments: HDFS-7420.000.patch, HDFS-7420.001.patch Many permission checks are in fact related to {{FSDirectory}} instead of {{FSNameSystem}}. It would be nice to move them to {{FSDirectory}} to reduce the effort of moving other functions from {{FSNameSystem}} to {{FSDirectory}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7331) Add Datanode network counts to datanode jmx page
[ https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222001#comment-14222001 ] Hudson commented on HDFS-7331: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1965 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1965/]) HDFS-7331. Add Datanode network counts to datanode jmx page. Contributed by Charles Lamb. (atm: rev 2d4f3e567e4bb8068c028de12df118a4f3fa6343) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeMetrics.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNodeMXBean.java Add Datanode network counts to datanode jmx page Key: HDFS-7331 URL: https://issues.apache.org/jira/browse/HDFS-7331 Project: Hadoop HDFS Issue Type: Improvement Components: datanode Reporter: Charles Lamb Assignee: Charles Lamb Priority: Minor Fix For: 2.7.0 Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch, HDFS-7331.003.patch, HDFS-7331.004.patch Add per-datanode counts to the datanode jmx page. For example, networkErrors could be exposed like this: {noformat} }, { ... DatanodeNetworkCounts : {\dn1\:{\networkErrors\:1}}, ... NamenodeAddresses : {\localhost\:\BP-1103235125-127.0.0.1-1415057084497\}, VolumeInfo : {\/tmp/hadoop-cwl/dfs/data/current\:{\freeSpace\:3092725760,\usedSpace\:28672,\reservedSpace\:0}}, ClusterId : CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e }, { {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony reassigned HDFS-6407: -- Assignee: Benoy Antony Assigning this feature to me. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Description: old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. was: old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Attachment: HDFS-6407.patch Attaching a patch which makes the tables on Namenode UI sortable. Tablesorter jquery plugin is used (http://mottie.github.io/tablesorter/docs/index.html). This plugin is also used in Apache Storm project as well as in several other products. LICENCE.txt is updated with license information related to Tablesorter jquery plugin. The actual changes in the html/js pages are minimal and mostly related to indenting. Testing is done manually. The screenshots are added to illustrate the feature. Both ascending and descending sorting is supported. Multiple columns can sorted simultaneously by holding down the SHIFT key and clicking a second, third or fourth column header. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222056#comment-14222056 ] Benoy Antony edited comment on HDFS-6407 at 11/22/14 5:42 PM: -- Assigning this feature to me since I was working on the feature and about to file another jira. was (Author: benoyantony): Assigning this feature to me. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Attachment: snapshots.png datanodes.png browse_directory.png new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Status: Patch Available (was: Open) new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222083#comment-14222083 ] Benoy Antony commented on HDFS-6407: To add sorting to do a new table, the following needs to be done. (More details in http://mottie.github.io/tablesorter/docs/index.html) 1. In the page containing table, include the css and js file {code} link rel=stylesheet type=text/css href=/static/tablesorter.default.css / script type=text/javascript src=/static/jquery.tablesorter.min.js /script {code} 2. Attach table sorter style on the table {code} table class=tablesorter-default {code} 3. Make sure that the table has THEAD and TBODY tags 4. Enable tablesorter to sort the table when the document is loaded. {code} $(.tablesorter-default).tablesorter({sortList: [[0,0]]}); {code} new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222092#comment-14222092 ] Hadoop QA commented on HDFS-6407: - {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12683163/snapshots.png against trunk revision a4df9ee. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8809//console This message is automatically generated. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222056#comment-14222056 ] Benoy Antony edited comment on HDFS-6407 at 11/22/14 5:52 PM: -- Assigning this feature to me since I was working on the feature and was about to file another jira. was (Author: benoyantony): Assigning this feature to me since I was working on the feature and about to file another jira. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Attachment: HDFS-6407.patch new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Attachment: (was: HDFS-6407.patch) new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-6407: --- Comment: was deleted (was: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12683163/snapshots.png against trunk revision a4df9ee. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8809//console This message is automatically generated.) new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
[ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-7303: --- Attachment: HDFS-7303.patch Attaching a simplified patch which adds the XferPort to the hostname to make it unique. If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab --- Key: HDFS-7303 URL: https://issues.apache.org/jira/browse/HDFS-7303 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.1 Reporter: Benoy Antony Assignee: Benoy Antony Priority: Minor Attachments: HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch If you start multiple datanodes on different ports on the the same host, only one of them appears in the NN UI’s datanode tab. While this is not a common scenario, there are still scenarios where you need to start multiple datanodes on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
[ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222123#comment-14222123 ] Hadoop QA commented on HDFS-7303: - {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12683167/HDFS-7303.patch against trunk revision a4df9ee. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8811//console This message is automatically generated. If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab --- Key: HDFS-7303 URL: https://issues.apache.org/jira/browse/HDFS-7303 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.1 Reporter: Benoy Antony Assignee: Benoy Antony Priority: Minor Attachments: HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch If you start multiple datanodes on different ports on the the same host, only one of them appears in the NN UI’s datanode tab. While this is not a common scenario, there are still scenarios where you need to start multiple datanodes on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
[ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-7303: --- Attachment: HDFS-7303.patch Attaching the patch after rebase. If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab --- Key: HDFS-7303 URL: https://issues.apache.org/jira/browse/HDFS-7303 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.1 Reporter: Benoy Antony Assignee: Benoy Antony Priority: Minor Attachments: HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch If you start multiple datanodes on different ports on the the same host, only one of them appears in the NN UI’s datanode tab. While this is not a common scenario, there are still scenarios where you need to start multiple datanodes on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7312) Update DistCp v1 to optionally not use tmp location
[ https://issues.apache.org/jira/browse/HDFS-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Prosser updated HDFS-7312: - Attachment: HDFS-7312.006.patch Update DistCp v1 to optionally not use tmp location --- Key: HDFS-7312 URL: https://issues.apache.org/jira/browse/HDFS-7312 Project: Hadoop HDFS Issue Type: Improvement Components: tools Affects Versions: 2.5.1 Reporter: Joseph Prosser Assignee: Joseph Prosser Priority: Minor Attachments: HDFS-7312.001.patch, HDFS-7312.002.patch, HDFS-7312.003.patch, HDFS-7312.004.patch, HDFS-7312.005.patch, HDFS-7312.006.patch, HDFS-7312.patch Original Estimate: 72h Remaining Estimate: 72h DistCp v1 currently copies files to a tmp location and then renames that to the specified destination. This can cause performance issues on filesystems such as S3. A -skiptmp flag will be added to bypass this step and copy directly to the destination. This feature mirrors a similar one added to HBase ExportSnapshot [HBASE-9|https://issues.apache.org/jira/browse/HBASE-9] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7312) Update DistCp v1 to optionally not use tmp location
[ https://issues.apache.org/jira/browse/HDFS-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222163#comment-14222163 ] Joseph Prosser commented on HDFS-7312: -- Added additional testcases and usage note. Removed extra line. This code has been tested on a cluster running Hadoop 2.0.0-cdh4.5.0 with S3 access using an S3 bucket. When using the -skiptmp flag I do not see these output lines: 14/11/22 15:20:07 INFO s3a.S3AFileSystem: Delete path s3a://BUCKETNAME/_distcp_tmp_57fmri - recursive true 14/11/22 15:20:07 INFO s3a.S3AFileSystem: Getting path status for s3a://BUCKETNAME/_distcp_tmp_57fmri (_distcp_tmp_57fmri) Update DistCp v1 to optionally not use tmp location --- Key: HDFS-7312 URL: https://issues.apache.org/jira/browse/HDFS-7312 Project: Hadoop HDFS Issue Type: Improvement Components: tools Affects Versions: 2.5.1 Reporter: Joseph Prosser Assignee: Joseph Prosser Priority: Minor Attachments: HDFS-7312.001.patch, HDFS-7312.002.patch, HDFS-7312.003.patch, HDFS-7312.004.patch, HDFS-7312.005.patch, HDFS-7312.006.patch, HDFS-7312.patch Original Estimate: 72h Remaining Estimate: 72h DistCp v1 currently copies files to a tmp location and then renames that to the specified destination. This can cause performance issues on filesystems such as S3. A -skiptmp flag will be added to bypass this step and copy directly to the destination. This feature mirrors a similar one added to HBase ExportSnapshot [HBASE-9|https://issues.apache.org/jira/browse/HBASE-9] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6407) new namenode UI, lost ability to sort columns in datanode tab
[ https://issues.apache.org/jira/browse/HDFS-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222196#comment-14222196 ] Hadoop QA commented on HDFS-6407: - {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12683166/HDFS-6407.patch against trunk revision a4df9ee. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:red}-1 release audit{color}. The applied patch generated 2 release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8810//testReport/ Release audit warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/8810//artifact/patchprocess/patchReleaseAuditProblems.txt Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8810//console This message is automatically generated. new namenode UI, lost ability to sort columns in datanode tab - Key: HDFS-6407 URL: https://issues.apache.org/jira/browse/HDFS-6407 Project: Hadoop HDFS Issue Type: Bug Components: namenode Affects Versions: 2.4.0 Reporter: Nathan Roberts Assignee: Benoy Antony Priority: Minor Attachments: HDFS-6407.patch, browse_directory.png, datanodes.png, snapshots.png old ui supported clicking on column header to sort on that column. The new ui seems to have dropped this very useful feature. There are a few tables in the Namenode UI to display datanodes information, directory listings and snapshots. When there are many items in the tables, it is useful to have ability to sort on the different columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
[ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1429#comment-1429 ] Hadoop QA commented on HDFS-7303: - {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12683168/HDFS-7303.patch against trunk revision a4df9ee. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.TestNameNodeMXBean {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8812//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8812//console This message is automatically generated. If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab --- Key: HDFS-7303 URL: https://issues.apache.org/jira/browse/HDFS-7303 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.1 Reporter: Benoy Antony Assignee: Benoy Antony Priority: Minor Attachments: HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch If you start multiple datanodes on different ports on the the same host, only one of them appears in the NN UI’s datanode tab. While this is not a common scenario, there are still scenarios where you need to start multiple datanodes on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
[ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HDFS-7303: --- Attachment: HDFS-7303.patch If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab --- Key: HDFS-7303 URL: https://issues.apache.org/jira/browse/HDFS-7303 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.1 Reporter: Benoy Antony Assignee: Benoy Antony Priority: Minor Attachments: HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch If you start multiple datanodes on different ports on the the same host, only one of them appears in the NN UI’s datanode tab. While this is not a common scenario, there are still scenarios where you need to start multiple datanodes on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
[ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222336#comment-14222336 ] Hadoop QA commented on HDFS-7303: - {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12683206/HDFS-7303.patch against trunk revision a4df9ee. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8813//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8813//console This message is automatically generated. If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab --- Key: HDFS-7303 URL: https://issues.apache.org/jira/browse/HDFS-7303 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.1 Reporter: Benoy Antony Assignee: Benoy Antony Priority: Minor Attachments: HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch, HDFS-7303.patch If you start multiple datanodes on different ports on the the same host, only one of them appears in the NN UI’s datanode tab. While this is not a common scenario, there are still scenarios where you need to start multiple datanodes on the same host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)