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 "Koji Noguchi (JIRA)" <ji...@apache.org> on 2007/10/18 20:53:50 UTC
[jira] Created: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Logging version number (and compiled date) at STARTUP_MSG
-----------------------------------------------------------
Key: HADOOP-2077
URL: https://issues.apache.org/jira/browse/HADOOP-2077
Project: Hadoop
Issue Type: Improvement
Components: dfs, mapred
Reporter: Koji Noguchi
Priority: Trivial
Fix For: 0.16.0
This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-2077:
----------------------------------
Status: Patch Available (was: Open)
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy reassigned HADOOP-2077:
-------------------------------------
Assignee: Arun C Murthy
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2077) Logging version number (and
compiled date) at STARTUP_MSG
Posted by "Koji Noguchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558635#action_12558635 ]
Koji Noguchi commented on HADOOP-2077:
--------------------------------------
+1 Thanks!
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch, HADOOP-2077_1_20080114.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2077) Logging version number (and
compiled date) at STARTUP_MSG
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559057#action_12559057 ]
Hudson commented on HADOOP-2077:
--------------------------------
Integrated in Hadoop-Nightly #366 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/366/])
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch, HADOOP-2077_1_20080114.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-2077:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this.
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch, HADOOP-2077_1_20080114.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-2077:
----------------------------------
Attachment: HADOOP-2077_0_20080110.patch
Simple fix.
I haven't gotten around to testing it much since svn.apache.org is _super_ slow...
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-2077:
----------------------------------
Attachment: HADOOP-2077_1_20080114.patch
Slight modification to the log-msg:
{noformat}
08/01/14 17:33:25 INFO dfs.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = neo/127.0.0.1
STARTUP_MSG: args = [-format]
STARTUP_MSG: version = 0.16.0-dev
STARTUP_MSG: build = http://svn.apache.org/repos/asf/lucene/hadoop/trunk -r 611760; compiled by 'arun' on Mon Jan 14 17:33:13 IST 2008
************************************************************/
{noformat}
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch, HADOOP-2077_1_20080114.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2077) Logging version number (and compiled
date) at STARTUP_MSG
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-2077:
----------------------------------
Attachment: HADOOP-2077_0_20080110.patch
Minor change in formatting of the output, which now looks like:
{noformat}
2008-01-10 03:57:15,143 INFO org.apache.hadoop.dfs.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = neo/127.0.0.1
STARTUP_MSG: args = []
STARTUP_MSG: version = 0.16.0-dev
STARTUP_MSG: subversion = http://svn.apache.org/repos/asf/lucene/hadoop/trunk -r 610541
STARTUP_MSG: compiled-by = arun on Thu Jan 10 03:57:03 IST 2008
************************************************************/
{noformat}
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2077) Logging version number (and
compiled date) at STARTUP_MSG
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558079#action_12558079 ]
Hadoop QA commented on HADOOP-2077:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12372845/HADOOP-2077_0_20080110.patch
against trunk revision r611056.
@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 failed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1544/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1544/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1544/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1544/console
This message is automatically generated.
> Logging version number (and compiled date) at STARTUP_MSG
> -----------------------------------------------------------
>
> Key: HADOOP-2077
> URL: https://issues.apache.org/jira/browse/HADOOP-2077
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs, mapred
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Trivial
> Fix For: 0.16.0
>
> Attachments: HADOOP-2077_0_20080110.patch, HADOOP-2077_0_20080110.patch
>
>
> This will help us figure out which version of hadoop we were running when looking back the logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.