hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2676) Maintaining cluster information across multiple job submissions
Date Mon, 25 Aug 2008 18:11:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625444#action_12625444

dhruba borthakur commented on HADOOP-2676:

I would like to implement Runping's proposal for tasktrackers. In this case, if a tasktracker
has run a consecutive number of tasks (configurable), then it determines that it is a bad
node and stops advertising it slots for some time. Once this quiet time period is over, it
clears up its state and starts advertising its slots again. The tasktracker does not keep
any persistent info regarding this, so restarting the tasktracker will clear up this state.


> Maintaining cluster information across multiple job submissions
> ---------------------------------------------------------------
>                 Key: HADOOP-2676
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2676
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.15.2
>            Reporter: Lohit Vijayarenu
> Could we have a way to maintain cluster state across multiple job submissions.
> Consider a scenario where we run multiple jobs in iteration on a cluster back to back.
The nature of the job is same, but input/output might differ. 
> Now, if a node is blacklisted in one iteration of job run, it would be useful to maintain
this information and blacklist this node for next iteration of job as well. 
> Another situation which we saw is, if there are failures less than mapred.map.max.attempts
in each iterations few nodes are never marked for blacklisting. But in we consider two or
three iterations, these nodes fail all jobs and should be taken out of cluster. This hampers
overall performance of the job.
> Could have have config variables something which matches a job type (provided by user)
and maintains the cluster status for that job type alone? 

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

View raw message