[
https://issues.apache.org/jira/browse/DRILL-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388562#comment-16388562
]
Kunal Khatua commented on DRILL-5028:
-------------------------------------
DRILL-5481 is an alternative to using the LocalFS if you do not need a long
term persistence of the profiles. This will have each Drillbit reserve memory
for a finite number of queries and keep only the k-most recent queries launched
from that Drillbit as a foreman.
The create-Table-As-Select command can be used to persist those metrics
periodically into the DFS for future top-level analysis.
> Opening profiles page from web ui gets very slow when a lot of history files
> have been stored in HDFS or Local FS.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DRILL-5028
> URL: https://issues.apache.org/jira/browse/DRILL-5028
> Project: Apache Drill
> Issue Type: Improvement
> Components: Functions - Drill
> Affects Versions: 1.8.0
> Reporter: Hongze Zhang
> Priority: Minor
> Fix For: Future
>
>
> We have a Drill cluster with 20+ Nodes and we store all history profiles in
> hdfs. Without doing periodically cleans for hdfs, the profiles page gets
> slower while serving more queries.
> Code from LocalPersistentStore.java uses fs.list(false, basePath) for
> fetching the latest 100 history profiles by default, I guess this operation
> blocks the page loading (Millions small files can be stored in the basePath),
> maybe we can try some other ways to reach the same goal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)