hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2026) Namenode prints out too many log lines for "Number of transactions"
Date Wed, 10 Oct 2007 22:09:51 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533889

Hadoop QA commented on HADOOP-2026:

+1 overall.  Here are the results of testing the latest attachment 
against trunk revision r583424.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/917/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/917/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/917/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/917/console

This message is automatically generated.

> Namenode prints out too many log lines for "Number of transactions"
> -------------------------------------------------------------------
>                 Key: HADOOP-2026
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2026
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.15.0
>         Attachments: tooManyLog.patch
> HADOOP-1942 introduced a log-line that prints the namenode transaction rate. The code
was supposed to be printing it out once every minute. But a bug caused it to appear once for
every transaction.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message