[
https://issues.apache.org/jira/browse/KYLIN-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963712#comment-16963712
]
wangxiaojing commented on KYLIN-4203:
-------------------------------------
@[~zhangyaqian]
Hello yaqian,
Thanks for your attention and reply. "When the number of building jobs
exceeds 'allowMaxBuildingSegments'，this cube can't submit new building jobs.
But if i wait for a segment to be build finished, this cube could submit new
segment to build." Yes，you are right ,but in most cases ,these jobs can never
run successfully, because at the time of disable cube, all the data the job
relies on, including the data on ZK and HDFS, has been deleted.
> Disable a real time cube and then enable it ,this cube may can't submit build
> job anymore
> -----------------------------------------------------------------------------------------
>
> Key: KYLIN-4203
> URL: https://issues.apache.org/jira/browse/KYLIN-4203
> Project: Kylin
> Issue Type: Bug
> Components: Real-time Streaming
> Affects Versions: Future
> Reporter: wangxiaojing
> Assignee: wangxiaojing
> Priority: Blocker
> Fix For: Future
>
> Attachments: image-2019-10-25-18-35-51-570.png
>
>
> First ,disable a real time streaming cube when the cube has max building jobs
> (default max job size is 10),then enable the cube。But this cube may can't
> subbmit new building jobs any more even if the kylin user have discarded the
> building jobs ,it logs "No left quota to build segments for cube". Because
> the amount of left quota one cube can submit building jobs is determined by
> this algorithm: allowMaxBuildingSegments - inBuildingSegments". The
> 'allowMaxBuildingSegments' is configed and the 'inBuildingSegments ' are the
> cube's not ready segments in hbase(perhaps some other storage).
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
