[ 
https://issues.apache.org/jira/browse/KUDU-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17326203#comment-17326203
 ] 

Redriver commented on KUDU-3223:
--------------------------------

implementation: https://gerrit.cloudera.org/#/c/17273/

> Total table size quota management for every user
> ------------------------------------------------
>
>                 Key: KUDU-3223
>                 URL: https://issues.apache.org/jira/browse/KUDU-3223
>             Project: Kudu
>          Issue Type: Wish
>            Reporter: Redriver
>            Priority: Major
>
> *Requirement description*
> In production environment, the quota management for total tables size and 
> single table size of a single user is necessary. If the quota is reached, the 
> write operation including insert and update is forbidden, only table 
> creation, scan and delete are allowed. 
> We need to allow admin to configure the quota for every user, monitor the 
> quota status, and stop the write operation with an error returned to client.
> So, I hope Kudu cli can list the status. Currently, the kudu table statistics 
> only gives the disk size and live row count. It is better improve this by 
> adding user name for table statistics, or create a new parameter to query 
> every table size for every user, and disable/enable a user's write privilege. 
> Can this be configured through Apache Ranger?
> *Typical scenarios*
>  # Some user has malicious operation to create a huge table, or many small 
> tables, as a result, the total table size exceeds the cluster's capacity, we 
> have to stop him in time. 
>  # When writing Kudu table through Flink, the streaming process is always 
> running, which means the Kudu table writing never stopped. If we do not have 
> a protection, the Kudu cluster will be exhausted someday. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to