[
https://issues.apache.org/jira/browse/HDFS-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386702#comment-14386702
]
Hadoop QA commented on HDFS-8001:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708147/HDFS-8001.patch
against trunk revision ae3e8c6.
{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: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-nfs.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/10110//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HDFS-Build/10110//console
This message is automatically generated.
> RpcProgramNfs3 : wrong parsing of dfs.blocksize
> -----------------------------------------------
>
> Key: HDFS-8001
> URL: https://issues.apache.org/jira/browse/HDFS-8001
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.6.0, 2.5.2
> Environment: any : windows, linux, etc.
> Reporter: Remi Catherinot
> Priority: Trivial
> Labels: easyfix
> Attachments: HDFS-8001.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> org/apache/hadoop/hdfs/nfs/nfs3/RpcProgramNfs3.java use Configuration.getLong
> to get the dfs.blocksize value, but it should use getLongBytes so it can
> handle syntax like 64m rather than pure numeric values. DataNode code &
> others all use getLongBytes.
> it's line 187 in source code.
> detected on version 2.5.2, checked version 2.6.0 which still has the bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
