Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 13769 invoked from network); 7 May 2008 04:54:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 May 2008 04:54:21 -0000 Received: (qmail 64145 invoked by uid 500); 7 May 2008 04:54:22 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 64110 invoked by uid 500); 7 May 2008 04:54:21 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 64099 invoked by uid 99); 7 May 2008 04:54:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 May 2008 21:54:21 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 May 2008 04:53:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D5D6C234C10D for ; Tue, 6 May 2008 21:53:55 -0700 (PDT) Message-ID: <1884410597.1210136035874.JavaMail.jira@brutus> Date: Tue, 6 May 2008 21:53:55 -0700 (PDT) From: "Amar Kamat (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3296) Some levels are skipped while creating the task cache in JobInProgress In-Reply-To: <1637218255.1208847081408.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594776#action_12594776 ] Amar Kamat commented on HADOOP-3296: ------------------------------------ bq. but I don't understand the purpose of the new counter (it could also use an entry in JobInProgress_Counter.properties, btw) .... The reason is that if there are more than 2 levels in the task cache (e.g local/rack/gateway/...) then there is no way to know if the maps were scheduled locally (at a level above rack) or not. Thanks for the review. > 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.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.