[
https://issues.apache.org/jira/browse/HDFS-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377377#comment-14377377
]
Hadoop QA commented on HDFS-3325:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704758/HDFS-3325.2.patch
against trunk revision 2c238ae.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 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.TestCheckpoint
org.apache.hadoop.tracing.TestTracing
org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA
org.apache.hadoop.hdfs.server.balancer.TestBalancer
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/10046//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HDFS-Build/10046//console
This message is automatically generated.
> When configuring "dfs.namenode.safemode.threshold-pct" to a value greater or
> equal to 1 there is mismatch in the UI report
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-3325
> URL: https://issues.apache.org/jira/browse/HDFS-3325
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: J.Andreina
> Assignee: J.Andreina
> Priority: Minor
> Attachments: HDFS-3325.1.patch, HDFS-3325.2.patch
>
>
> When dfs.namenode.safemode.threshold-pct is configured to n
> Namenode will be in safemode until n percentage of blocks that should satisfy
> the minimal replication requirement defined by
> dfs.namenode.replication.min is reported to namenode
> But in UI it displays that n percentage of total blocks + 1 blocks are
> additionally needed
> to come out of the safemode
> Scenario 1:
> ============
> Configurations:
> dfs.namenode.safemode.threshold-pct = 2
> dfs.replication = 2
> dfs.namenode.replication.min =2
> Step 1: Start NN,DN1,DN2
> Step 2: Write a file "a.txt" which has got 167 blocks
> step 3: Stop NN,DN1,DN2
> Step 4: start NN
> In UI report the Number of blocks needed to come out of safemode and number
> of blocks actually present is different.
> {noformat}
> Cluster Summary
> Security is OFF
> Safe mode is ON. The reported blocks 0 needs additional 335 blocks to reach
> the threshold 2.0000 of total blocks 167. Safe mode will be turned off
> automatically.
> 2 files and directories, 167 blocks = 169 total.
> Heap Memory used 57.05 MB is 2% of Commited Heap Memory 2 GB. Max Heap Memory
> is 2 GB.
> Non Heap Memory used 23.37 MB is 17% of Commited Non Heap Memory 130.44 MB.
> Max Non Heap Memory is 176 MB.{noformat}
> Scenario 2:
> ===========
> Configurations:
> dfs.namenode.safemode.threshold-pct = 1
> dfs.replication = 2
> dfs.namenode.replication.min =2
> Step 1: Start NN,DN1,DN2
> Step 2: Write a file "a.txt" which has got 167 blocks
> step 3: Stop NN,DN1,DN2
> Step 4: start NN
> In UI report the Number of blocks needed to come out of safemode and number
> of blocks actually present is different
> {noformat}
> Cluster Summary
> Security is OFF
> Safe mode is ON. The reported blocks 0 needs additional 168 blocks to reach
> the threshold 1.0000 of total blocks 167. Safe mode will be turned off
> automatically.
> 2 files and directories, 167 blocks = 169 total.
> Heap Memory used 56.2 MB is 2% of Commited Heap Memory 2 GB. Max Heap Memory
> is 2 GB.
> Non Heap Memory used 23.37 MB is 17% of Commited Non Heap Memory 130.44 MB.
> Max Non Heap Memory is 176 MB.{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
