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-4304) Make FSEditLogOp.MAX_OP_SIZE configurable
Date Thu, 13 Dec 2012 00:19:21 GMT

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

Hadoop QA commented on HDFS-4304:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12560658/HDFS-4304.003.patch
  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 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}.  The javadoc tool did not generate any 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
hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3653//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3653//console

This message is automatically generated.
                
> Make FSEditLogOp.MAX_OP_SIZE configurable
> -----------------------------------------
>
>                 Key: HDFS-4304
>                 URL: https://issues.apache.org/jira/browse/HDFS-4304
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0, 2.0.3-alpha
>            Reporter: Todd Lipcon
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-4304.001.patch, HDFS-4304.002.patch, HDFS-4304.003.patch
>
>
> Today we ran into an issue where a NN had logged a very large op, greater than the 1.5MB
MAX_OP_SIZE constant. In order to successfully load the edits, we had to patch with a larger
constant. This constant should be configurable so that we wouldn't have to recompile in these
odd cases. Additionally, I think the default should be bumped a bit higher, since it's only
a safeguard against OOME, and people tend to run NNs with multi-GB heaps.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message