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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2008/03/24 17:39:24 UTC
[jira] Created: (HADOOP-3080) Remove flush calls from JobHistory
Remove flush calls from JobHistory
----------------------------------
Key: HADOOP-3080
URL: https://issues.apache.org/jira/browse/HADOOP-3080
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.17.0
Reporter: Devaraj Das
Assignee: Amareshwari Sriramadasu
Priority: Critical
Fix For: 0.17.0
The flush calls from JobHistory should be removed. This has performance impact when lots of events are being logged to the history files since the JT lock (e.g. lostTracker where the tracker had ran a lot of tasks, and we call failedTask in a loop, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3080) Remove flush calls from JobHistory
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-3080:
--------------------------------------------
Attachment: patch-3080.txt
> Remove flush calls from JobHistory
> ----------------------------------
>
> Key: HADOOP-3080
> URL: https://issues.apache.org/jira/browse/HADOOP-3080
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-3080.txt
>
>
> The flush calls from JobHistory should be removed. This has performance impact when lots of events are being logged to the history files since the JT lock (e.g. lostTracker where the tracker had ran a lot of tasks, and we call failedTask in a loop, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3080) Remove flush calls from JobHistory
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-3080:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Amareshwari!
> Remove flush calls from JobHistory
> ----------------------------------
>
> Key: HADOOP-3080
> URL: https://issues.apache.org/jira/browse/HADOOP-3080
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-3080.txt
>
>
> The flush calls from JobHistory should be removed. This has performance impact when lots of events are being logged to the history files since the JT lock (e.g. lostTracker where the tracker had ran a lot of tasks, and we call failedTask in a loop, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3080) Remove flush calls from JobHistory
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-3080:
--------------------------------------------
Status: Patch Available (was: Open)
> Remove flush calls from JobHistory
> ----------------------------------
>
> Key: HADOOP-3080
> URL: https://issues.apache.org/jira/browse/HADOOP-3080
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-3080.txt
>
>
> The flush calls from JobHistory should be removed. This has performance impact when lots of events are being logged to the history files since the JT lock (e.g. lostTracker where the tracker had ran a lot of tasks, and we call failedTask in a loop, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3080) Remove flush calls from JobHistory
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581846#action_12581846 ]
Hadoop QA commented on HADOOP-3080:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12378540/patch-3080.txt
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit 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://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2044/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2044/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2044/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2044/console
This message is automatically generated.
> Remove flush calls from JobHistory
> ----------------------------------
>
> Key: HADOOP-3080
> URL: https://issues.apache.org/jira/browse/HADOOP-3080
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-3080.txt
>
>
> The flush calls from JobHistory should be removed. This has performance impact when lots of events are being logged to the history files since the JT lock (e.g. lostTracker where the tracker had ran a lot of tasks, and we call failedTask in a loop, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3080) Remove flush calls from JobHistory
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581921#action_12581921 ]
Hudson commented on HADOOP-3080:
--------------------------------
Integrated in Hadoop-trunk #441 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/441/])
> Remove flush calls from JobHistory
> ----------------------------------
>
> Key: HADOOP-3080
> URL: https://issues.apache.org/jira/browse/HADOOP-3080
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-3080.txt
>
>
> The flush calls from JobHistory should be removed. This has performance impact when lots of events are being logged to the history files since the JT lock (e.g. lostTracker where the tracker had ran a lot of tasks, and we call failedTask in a loop, etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.