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

Hadoop QA commented on HDFS-6108:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12635058/HDFS-6108-v2.txt
  against trunk revision .

    {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 1.3.9) 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/6412//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6412//console

This message is automatically generated.

> make the length of the range in sync_file_range() configurable
> --------------------------------------------------------------
>
>                 Key: HDFS-6108
>                 URL: https://issues.apache.org/jira/browse/HDFS-6108
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 3.0.0, 2.3.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>         Attachments: HDFS-6108-v2.txt, HDFS-6108.txt
>
>
> Current codebase has a hard code value for sync_file_range system call, we'd 
> better to make it configurable, since different scenario probably has a 
> different/better value for it. (ps: i found it's 1 * 1024 * 1024 in fb-20 
> branch)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to