Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 182A31024A for ; Sun, 8 Dec 2013 04:40:10 +0000 (UTC) Received: (qmail 65077 invoked by uid 500); 8 Dec 2013 04:40:09 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 65038 invoked by uid 500); 8 Dec 2013 04:40:06 -0000 Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.incubator.apache.org Delivered-To: mailing list dev@tajo.incubator.apache.org Received: (qmail 65029 invoked by uid 99); 8 Dec 2013 04:40:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Dec 2013 04:40:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 08 Dec 2013 04:39:59 +0000 Received: (qmail 65013 invoked by uid 99); 8 Dec 2013 04:39:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Dec 2013 04:39:36 +0000 Date: Sun, 8 Dec 2013 04:39:36 +0000 (UTC) From: "Keuntae Park (JIRA)" To: dev@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (TAJO-385) Refactoring TaskScheduler to assign multiple fragments 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/TAJO-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842408#comment-13842408 ] Keuntae Park edited comment on TAJO-385 at 12/8/13 4:37 AM: ------------------------------------------------------------ +1 for this great idea. I think it is very important to determine the proper number of fragments assigned to one worker at a time and relationship between those fragments. was (Author: sirpkt): +1 for this great idea. I think it is very important to determine the number of fragments assigned to one worker at a time and relationship between those fragments. > Refactoring TaskScheduler to assign multiple fragments > ------------------------------------------------------ > > Key: TAJO-385 > URL: https://issues.apache.org/jira/browse/TAJO-385 > Project: Tajo > Issue Type: Improvement > Components: master > Affects Versions: 0.8-incubating > Reporter: Jihoon Son > Assignee: Jihoon Son > > In the current implementation, each task processes only one fragment. > However, processing multiple fragments in a task will increase the query processing performance according to the storage layout and the user queries. > In this issue, TaskScheduler is refactored to enable assigning multiple fragments to each task. > Followings should be contained. > * Schedule Fragments instead of QueryUnits in TaskScheduler > ** The QueryUnit creation is postponed until TaskScheduler receives task requests from workers. > ** When TaskScheduler receives task requests from workers, it dynamically creates an QueryUnit and assigns one or more fragments. > ** The fragment scheduling should take into account the disk load balancing. -- This message was sent by Atlassian JIRA (v6.1#6144)