You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "kangkaisen (JIRA)" <ji...@apache.org> on 2017/01/18 08:17:26 UTC

[jira] [Resolved] (KYLIN-2389) Improve resource utilization for DistributedScheduler

     [ https://issues.apache.org/jira/browse/KYLIN-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kangkaisen resolved KYLIN-2389.
-------------------------------
       Resolution: Fixed
    Fix Version/s: v2.0.0

> Improve resource utilization for DistributedScheduler
> -----------------------------------------------------
>
>                 Key: KYLIN-2389
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2389
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Job Engine
>    Affects Versions: v2.0.0
>            Reporter: kangkaisen
>            Assignee: kangkaisen
>             Fix For: v2.0.0
>
>
> Currently, in DistributedScheduler we lock segment in JobService, which will make the job of segment only schedule in jobServer that the job submitted and    could not fully utilize the threadPool resource of all jobServers.
> For example, we have two jobServer and the max concurrent jobs is 10, if we continuously submit 20 jobs to jobServer1, there will be only 10 jobs running at the same time not 20 and will no job running in jobServer2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)