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 "Lohit Vijayarenu (JIRA)" <ji...@apache.org> on 2008/09/11 02:46:46 UTC
[jira] Created: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME is
not initialized properly
JobHisotry::JOBTRACKER_START_TIME is not initialized properly
-------------------------------------------------------------
Key: HADOOP-4155
URL: https://issues.apache.org/jira/browse/HADOOP-4155
Project: Hadoop Core
Issue Type: Bug
Reporter: Lohit Vijayarenu
JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME is
not initialized properly
Posted by "Lohit Vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lohit Vijayarenu updated HADOOP-4155:
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.19.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this.
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Fix For: 0.19.0
>
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME
is not initialized properly
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630349#action_12630349 ]
Hadoop QA commented on HADOOP-4155:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12389906/HADOOP-4155.patch
against trunk revision 693705.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3246/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3246/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3246/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3246/console
This message is automatically generated.
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME
is not initialized properly
Posted by "Lohit Vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630052#action_12630052 ]
Lohit Vijayarenu commented on HADOOP-4155:
------------------------------------------
I am trying to link 'Analyze the Job' page to jobdetails.jsp and see that the jobTrackerID used is different. What would be the right way to initialize JobHistory so that it uses JobTracker's startTime.
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME is
not initialized properly
Posted by "Lohit Vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lohit Vijayarenu updated HADOOP-4155:
-------------------------------------
Attachment: HADOOP-4155.patch
Attached patch changes this. No tests as this just changes initialization of variable.
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME
is not initialized properly
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630108#action_12630108 ]
Amareshwari Sriramadasu commented on HADOOP-4155:
-------------------------------------------------
Patch looks good to me.
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME is
not initialized properly
Posted by "Robert Chansler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-4155:
------------------------------------
Component/s: mapred
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Fix For: 0.19.0
>
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME is
not initialized properly
Posted by "Lohit Vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lohit Vijayarenu updated HADOOP-4155:
-------------------------------------
Status: Patch Available (was: Open)
Thanks Amareshwari, making it PA
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-4155) JobHisotry::JOBTRACKER_START_TIME is
not initialized properly
Posted by "Lohit Vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lohit Vijayarenu reassigned HADOOP-4155:
----------------------------------------
Assignee: Lohit Vijayarenu
> JobHisotry::JOBTRACKER_START_TIME is not initialized properly
> -------------------------------------------------------------
>
> Key: HADOOP-4155
> URL: https://issues.apache.org/jira/browse/HADOOP-4155
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Attachments: HADOOP-4155.patch
>
>
> JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.