[
https://issues.apache.org/jira/browse/KYLIN-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686322#comment-17686322
]
Yaguang Jia commented on KYLIN-5433:
------------------------------------
h2. Dev Design
{{StorageInfoCollector}} This interface is a unified entry point for the total
amount of storage quota, the amount used, and the amount to be cleared. The
relevant calculations are done by implementing its collect method. Therefore.
1. add a default method to this excuse to determine whether the storage quota
switch {{kylin.storage.check-quota-enabled }}(default false, that is, off) is
on. If it is on, the calculation will be performed, if not directly return not
to calculate.
2, the current version: in order to prevent the need to use the storage quota
everywhere to calculate the current usage, causing pressure on hdfs.
HdfsCapacityMetrics here using a thread pool regularly (default 5min
{{{}kylin.metrics.hdfs-periodic-calculation-interval{}}}) calculations, and the
results will be written down other threads to get the results directly, without
calculation. (This function is enabled by default
{{{}kylin.metrics.hdfs-periodic-calculation-enabled{}}}). In turn off the
storage quota function, the above features are turned off. When the storage
quota function is turned on, it still follows the old version logic.
> Add system-level parameters, and the storage quota function is turned off by
> default
> ------------------------------------------------------------------------------------
>
> Key: KYLIN-5433
> URL: https://issues.apache.org/jira/browse/KYLIN-5433
> Project: Kylin
> Issue Type: Improvement
> Affects Versions: 5.0-alpha
> Reporter: Yaguang Jia
> Assignee: Yaguang Jia
> Priority: Major
> Fix For: 5.0-alpha
>
>
> As the storage quota is not used much, add system-level parameters, the
> storage quota is turned off by default, and can be turned on separately if
> needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
