hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5725) TaskTracker shuold run user tasks nicely in the local machine
Date Fri, 24 Apr 2009 06:13:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702254#action_12702254
] 

Arun C Murthy commented on HADOOP-5725:
---------------------------------------

bq. I had jobs with tasks expected to run ~30 minutes. However, there were some CPU intensive
tasks from other jobs running in the cluster. If my task got scheduled to the same machine
with these CPU intensive tasks, my tasks might run 2 or more hours. In some cases, the task
got timeout or lost TaskTracker.

Nicholas - did you require higher memory for your tasks too? If so, you could use the memory-requirement
control knob...

----

Overall, I agree with Hong - the better solution is for the JobTracker to dynamically react
to the load on the TaskTrackers and throttle slots etc.

> TaskTracker shuold run user tasks nicely in the local machine
> -------------------------------------------------------------
>
>                 Key: HADOOP-5725
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5725
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Tsz Wo (Nicholas), SZE
>
> If one task tried to use all CPUs in a local machine, all other tasks or processes (includes
tasktracker and datanode daemons) may hardly get a chance to run.

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


Mime
View raw message