[
https://issues.apache.org/jira/browse/DRILL-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818218#comment-16818218
]
ASF GitHub Bot commented on DRILL-2362:
---------------------------------------
kkhatua commented on issue #1750: DRILL-2362: Profile Mgmt
URL: https://github.com/apache/drill/pull/1750#issuecomment-483352093
@arina-ielchiieva I'm looking for a suggestion on how to manage existing
profiles.
Currently, during startup, we automatically index any profiles in the root
of the `profiles` dir into their respective location. As a default, I have set
it at 1000, and the Drillbits syncrhonize if the profile dir is on a DFS.
However, I am not sure if we should automatically index any new profile that
has been copy-pasted into the root dir. For e.g., we might get a profile from a
JIRA and would like to view it. Should we leave it there (and try to render it)
or should we index it ASAP ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Drill should manage Query Profiling archiving
> ---------------------------------------------
>
> Key: DRILL-2362
> URL: https://issues.apache.org/jira/browse/DRILL-2362
> Project: Apache Drill
> Issue Type: New Feature
> Components: Storage - Other
> Affects Versions: 0.7.0
> Reporter: Chris Westin
> Assignee: Kunal Khatua
> Priority: Major
> Fix For: 1.17.0
>
>
> We collect query profile information for analysis purposes, but we keep it
> forever. At this time, for a few queries, it isn't a problem. But as users
> start putting Drill into production, automated use via other applications
> will make this grow quickly. We need to come up with a retention policy
> mechanism, with suitable settings administrators can use, and implement it so
> that this data can be cleaned up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)