You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2018/06/19 13:24:00 UTC

[jira] [Updated] (KYLIN-3353) Merge job should not be blocked by "kylin.cube.max-building-segments"

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

Shaofeng SHI updated KYLIN-3353:
--------------------------------
    Fix Version/s:     (was: v2.4.0)

> Merge job should not be blocked by "kylin.cube.max-building-segments"
> ---------------------------------------------------------------------
>
>                 Key: KYLIN-3353
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3353
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Job Engine
>            Reporter: Shaofeng SHI
>            Assignee: Shaofeng SHI
>            Priority: Minor
>
> Currently there is a config "kylin.cube.max-building-segments" (default be 10) set the max. jobs for a cube.
> In a frequently build case, that is possible that have 10 segments being built concurrently. Then there is no room for the merge jobs. If the merge job is blocked, more segments will be accumulated, and then impact on the query performance.
>  
> So I suggest to disable the checking for merge jobs.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)