[jira] [Updated] (HDFS-1732) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing
[ https://issues.apache.org/jira/browse/HDFS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-1732: --- Fix Version/s: (was: 0.24.0) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing -- Key: HDFS-1732 URL: https://issues.apache.org/jira/browse/HDFS-1732 Project: Hadoop HDFS Issue Type: Sub-task Components: namenode Affects Versions: 0.22.0 Reporter: Matt Foley Assignee: Matt Foley Attachments: IBRBenchmark_apachetrunk_v8.patch, IBRBenchmark_apachetrunk_v9.patch Rework NNThroughputBenchmark to provide more detailed info about Initial Block Report (IBR) processing time, as a function of number of nodes, number of unique blocks, and total number of replicas. Allow both direct local communication and remote and local RPC, so we can see how much impact RPC overhead has on IBR processing time. Also plug some holes in performance-specific logging of Block Report processing, so that consistent and complete data are logged from both Namenode and Datanode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-1732) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing
[ https://issues.apache.org/jira/browse/HDFS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-1732: --- Status: Open (was: Patch Available) Cancelling patch as it no longer applies to trunk. Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing -- Key: HDFS-1732 URL: https://issues.apache.org/jira/browse/HDFS-1732 Project: Hadoop HDFS Issue Type: Sub-task Components: namenode Affects Versions: 0.22.0 Reporter: Matt Foley Assignee: Matt Foley Attachments: IBRBenchmark_apachetrunk_v8.patch, IBRBenchmark_apachetrunk_v9.patch Rework NNThroughputBenchmark to provide more detailed info about Initial Block Report (IBR) processing time, as a function of number of nodes, number of unique blocks, and total number of replicas. Allow both direct local communication and remote and local RPC, so we can see how much impact RPC overhead has on IBR processing time. Also plug some holes in performance-specific logging of Block Report processing, so that consistent and complete data are logged from both Namenode and Datanode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-1732) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing
[ https://issues.apache.org/jira/browse/HDFS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1732: - Issue Type: Sub-task (was: Improvement) Parent: HDFS-2126 Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing -- Key: HDFS-1732 URL: https://issues.apache.org/jira/browse/HDFS-1732 Project: Hadoop HDFS Issue Type: Sub-task Components: name-node Affects Versions: 0.22.0 Reporter: Matt Foley Assignee: Matt Foley Fix For: 0.23.0 Attachments: IBRBenchmark_apachetrunk_v8.patch, IBRBenchmark_apachetrunk_v9.patch Rework NNThroughputBenchmark to provide more detailed info about Initial Block Report (IBR) processing time, as a function of number of nodes, number of unique blocks, and total number of replicas. Allow both direct local communication and remote and local RPC, so we can see how much impact RPC overhead has on IBR processing time. Also plug some holes in performance-specific logging of Block Report processing, so that consistent and complete data are logged from both Namenode and Datanode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1732) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing
[ https://issues.apache.org/jira/browse/HDFS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1732: - Attachment: IBRBenchmark_apachetrunk_v9.patch Update to latest trunk. Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing -- Key: HDFS-1732 URL: https://issues.apache.org/jira/browse/HDFS-1732 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Affects Versions: 0.22.0 Reporter: Matt Foley Assignee: Matt Foley Fix For: 0.23.0 Attachments: IBRBenchmark_apachetrunk_v8.patch, IBRBenchmark_apachetrunk_v9.patch Rework NNThroughputBenchmark to provide more detailed info about Initial Block Report (IBR) processing time, as a function of number of nodes, number of unique blocks, and total number of replicas. Allow both direct local communication and remote and local RPC, so we can see how much impact RPC overhead has on IBR processing time. Also plug some holes in performance-specific logging of Block Report processing, so that consistent and complete data are logged from both Namenode and Datanode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HDFS-1732) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing
[ https://issues.apache.org/jira/browse/HDFS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1732: - Attachment: IBRBenchmark_apachetrunk_v8.patch Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing -- Key: HDFS-1732 URL: https://issues.apache.org/jira/browse/HDFS-1732 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Affects Versions: 0.22.0 Reporter: Matt Foley Assignee: Matt Foley Fix For: 0.23.0 Attachments: IBRBenchmark_apachetrunk_v8.patch Rework NNThroughputBenchmark to provide more detailed info about Initial Block Report (IBR) processing time, as a function of number of nodes, number of unique blocks, and total number of replicas. Allow both direct local communication and remote and local RPC, so we can see how much impact RPC overhead has on IBR processing time. Also plug some holes in performance-specific logging of Block Report processing, so that consistent and complete data are logged from both Namenode and Datanode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HDFS-1732) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing
[ https://issues.apache.org/jira/browse/HDFS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1732: - Fix Version/s: 0.23.0 Status: Patch Available (was: Open) Enhance NNThroughputBenchmark to observe scale-dependent changes in IBR processing -- Key: HDFS-1732 URL: https://issues.apache.org/jira/browse/HDFS-1732 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Affects Versions: 0.22.0 Reporter: Matt Foley Assignee: Matt Foley Fix For: 0.23.0 Attachments: IBRBenchmark_apachetrunk_v8.patch Rework NNThroughputBenchmark to provide more detailed info about Initial Block Report (IBR) processing time, as a function of number of nodes, number of unique blocks, and total number of replicas. Allow both direct local communication and remote and local RPC, so we can see how much impact RPC overhead has on IBR processing time. Also plug some holes in performance-specific logging of Block Report processing, so that consistent and complete data are logged from both Namenode and Datanode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
