[
https://issues.apache.org/jira/browse/TAJO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919101#comment-13919101
]
Tajo QA commented on TAJO-647:
------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12632442/TAJO-647.patch
against master revision f4a9fd1.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:red}-1 tests included.{color} The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac.{color} The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc.{color} The applied patch generated 49 javadoc
warnings (more than the trunk's current 48 warnings).
{color:green}+1 checkstyle.{color} The patch generated 0 code style errors.
{color:red}-1 findbugs.{color} The patch appears to introduce 183 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit.{color} The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests.{color} The patch passed unit tests in
tajo-core/tajo-core-backend.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/177//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/177//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/177//console
This message is automatically generated.
> Work unbalance on disk scheduling of DefaultScheduler
> ------------------------------------------------------
>
> Key: TAJO-647
> URL: https://issues.apache.org/jira/browse/TAJO-647
> Project: Tajo
> Issue Type: Bug
> Components: resource manager
> Affects Versions: 0.8-incubating
> Reporter: Jinho Kim
> Assignee: Jinho Kim
> Attachments: TAJO-647.patch
>
>
> The main problem is that localAllocation does not find next lowest volume.
> and it will assign to remote in rack.
> We should control the remote tasks.
> * Leaf scheduling priorities
> 1. tasks in a volume of host
> 2. unknown disk, non-splitable in local host
> 3. remote tasks in rack. (consider the remaining tasks)
> 4. random remote tasks. (tail concurrency control of scheduled tasks)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
