Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 61765 invoked from network); 11 Nov 2010 22:18:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Nov 2010 22:18:15 -0000 Received: (qmail 20684 invoked by uid 500); 11 Nov 2010 22:18:46 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 20645 invoked by uid 500); 11 Nov 2010 22:18:46 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 20637 invoked by uid 99); 11 Nov 2010 22:18:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Nov 2010 22:18:46 +0000 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.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Nov 2010 22:18:41 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oABMII0V025969 for ; Thu, 11 Nov 2010 22:18:18 GMT Message-ID: <1599572.37181289513898495.JavaMail.jira@thor> Date: Thu, 11 Nov 2010 17:18:18 -0500 (EST) From: "Hong Tang (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-1608) Allow users to do speculative execution of a task manually MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931233#action_12931233 ] Hong Tang commented on MAPREDUCE-1608: -------------------------------------- bq. But when there is a manual-speculate-now button, it can override the system-specified speculation heuristics for that task. To go a ste further, the system can actually learn from the user-specified-speculation on how to automatically make the heuristics better, i.e. crowd-sourcing to the rescue! I agree that knowledgeable users have more information about their programs and probably can speculate more accurately. Such info may also be used for the verification (future tuning) of speculative execution algorithms (e.g. through simulation). So here is my +1 on the idea. > Allow users to do speculative execution of a task manually > ---------------------------------------------------------- > > Key: MAPREDUCE-1608 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1608 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Reporter: Scott Chen > Assignee: Scott Chen > > Speculative execution improves the latency of the job. Sometimes the job has few very slow reducers. Spending a little more resource on speculative tasks can improve the latency a lot. It will be nice that the users can manually select one task and force the speculative execution on that task just like we can manually kill/fail task. > The proposal is add link says "speculate" in taskdetails.jsp page where we do "kill/fail". > Thoughts? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.