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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2008/05/07 10:42:02 UTC
[jira] Updated: (HADOOP-3296) Some levels are skipped while
creating the task cache in JobInProgress
[ https://issues.apache.org/jira/browse/HADOOP-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-3296:
-------------------------------
Attachment: HADOOP-3296-v2.patch
> Some levels are skipped while creating the task cache in JobInProgress
> ----------------------------------------------------------------------
>
> Key: HADOOP-3296
> URL: https://issues.apache.org/jira/browse/HADOOP-3296
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Attachments: HADOOP-3296-v2.patch, HADOOP-3296.patch
>
>
> Consider the following piece of code
> {code:title=JobInProgress.createCache()|borderStyle=solid}
> Node node = jobtracker.resolveAndAddToTopology(host);
> for (int j = 0; j < maxLevel; j++) {
> node = JobTracker.getParentNode(node, j);
> .....
> {code}
> With {{maxLevel > 2}} the caches will be created in the following order
> ||j||node-level||
> |0|0|
> |1|1|
> |2|3|
> |3|6|
> which is not as desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.