You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Luke Han (JIRA)" <ji...@apache.org> on 2015/08/25 14:44:50 UTC

[jira] [Updated] (KYLIN-558) Quota management support by project

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

Luke Han updated KYLIN-558:
---------------------------
    Fix Version/s:     (was: v1.0)
                   v1.1

> Quota management support by project
> -----------------------------------
>
>                 Key: KYLIN-558
>                 URL: https://issues.apache.org/jira/browse/KYLIN-558
>             Project: Kylin
>          Issue Type: New Feature
>          Components: General
>            Reporter: Luke Han
>            Assignee: Luke Han
>             Fix For: v1.1
>
>
> Cube technology is using space swap time: pre-calculate result and store to somewhere for further query, since the result already there, there's no runtime scan in query phase.
> Although Kylin have good design to optimize final cube size, but in reality, storage and computing resources always have limitation. To well balance between each project, this feature will enable quota by project:
> 1. Entire system will have one setting for total quota, could set by admin or read from HBase/Hive
> 2. Each project will have quota setting, default value will be set in kylin.propertiies file
> 3. Admin can update that value of each project.
> 4. Every cube build job should inquire it's project quota and compare to used storage, denied process to next step if the used storage already exceed quota
> 5. System should alert project owner and admin when used storage close to 85% of quota or exceeded 
> Same policy also should extend to MR job, Hive and others.
> Target Release: v0.7.3 - capacity and automation



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