You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/10/10 22:50:50 UTC
[jira] Created: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
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
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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this.
> 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.
[jira] Commented: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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
http://issues.apache.org/jira/secure/attachment/12367521/tooManyLog.patch
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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Fix Version/s: 0.15.0
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Attachment: (was: tooManyLog.patch)
> 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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Attachment: tooManyLog.patch
Incorporated Raghu's comments.
> 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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Attachment: tooManyLog.patch
> 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
> 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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Status: Open (was: Patch Available)
> 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.
[jira] Commented: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534329 ]
Hudson commented on HADOOP-2026:
--------------------------------
Integrated in Hadoop-Nightly #269 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/269/])
> 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.
[jira] Commented: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533877 ]
Raghu Angadi commented on HADOOP-2026:
--------------------------------------
Could also initialize {{lastPrintTime}}? With out this first stats are printed only after first roll of the edit logs.
> 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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Priority: Blocker (was: Major)
> 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.
[jira] Commented: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534006 ]
Hadoop QA commented on HADOOP-2026:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12367534/tooManyLog.patch
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/921/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/921/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/921/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/921/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.
[jira] Updated: (HADOOP-2026) Namenode prints out too many log
lines for "Number of transactions"
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-2026:
-------------------------------------
Status: Patch Available (was: Open)
> 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.