hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7980) Incremental BlockReport will dramatically slow down the startup of a namenode
Date Tue, 28 Apr 2015 07:35:07 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516592#comment-14516592
] 

Hadoop QA commented on HDFS-7980:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 29s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags.
|
| {color:green}+1{color} | tests included |   0m  0s | The patch appears to include 1 new
or modified test files. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace.
|
| {color:green}+1{color} | javac |   7m 28s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 37s | There were no new javadoc warning messages.
|
| {color:green}+1{color} | release audit |   0m 22s | The applied patch does not increase
the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   7m 45s | There were no new checkstyle issues. |
| {color:green}+1{color} | install |   1m 31s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 33s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   3m  6s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | native |   3m 12s | Pre-build of native portion |
| {color:red}-1{color} | hdfs tests | 185m 45s | Tests failed in hadoop-hdfs. |
| | | 233m 59s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.hdfs.server.blockmanagement.TestDatanodeManager |
|   | hadoop.hdfs.server.namenode.ha.TestHASafeMode |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12728688/HDFS-7980.003.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / feb68cb |
| hadoop-hdfs test log | https://builds.apache.org/job/PreCommit-HDFS-Build/10426/artifact/patchprocess/testrun_hadoop-hdfs.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-HDFS-Build/10426/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf909.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep
3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/10426/console |


This message was automatically generated.

> Incremental BlockReport will dramatically slow down the startup of  a namenode
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-7980
>                 URL: https://issues.apache.org/jira/browse/HDFS-7980
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Hui Zheng
>            Assignee: Walter Su
>         Attachments: HDFS-7980.001.patch, HDFS-7980.002.patch, HDFS-7980.003.patch
>
>
> In the current implementation the datanode will call the reportReceivedDeletedBlocks()
method that is a IncrementalBlockReport before calling the bpNamenode.blockReport() method.
So in a large(several thousands of datanodes) and busy cluster it will slow down(more than
one hour) the startup of namenode. 
> {code}
> List<DatanodeCommand> blockReport() throws IOException {
>     // send block report if timer has expired.
>     final long startTime = now();
>     if (startTime - lastBlockReport <= dnConf.blockReportInterval) {
>       return null;
>     }
>     final ArrayList<DatanodeCommand> cmds = new ArrayList<DatanodeCommand>();
>     // Flush any block information that precedes the block report. Otherwise
>     // we have a chance that we will miss the delHint information
>     // or we will report an RBW replica after the BlockReport already reports
>     // a FINALIZED one.
>     reportReceivedDeletedBlocks();
>     lastDeletedReport = startTime;
>     .........
>         // Send the reports to the NN.
>     int numReportsSent = 0;
>     int numRPCs = 0;
>     boolean success = false;
>     long brSendStartTime = now();
>     try {
>       if (totalBlockCount < dnConf.blockReportSplitThreshold) {
>         // Below split threshold, send all reports in a single message.
>         DatanodeCommand cmd = bpNamenode.blockReport(
>             bpRegistration, bpos.getBlockPoolId(), reports);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message