[
https://issues.apache.org/jira/browse/HIVE-20025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576568#comment-16576568
]
ASF GitHub Bot commented on HIVE-20025:
---------------------------------------
Github user sankarh closed the pull request at:
https://github.com/apache/hive/pull/384
> Clean-up of event files created by HiveProtoLoggingHook.
> --------------------------------------------------------
>
> Key: HIVE-20025
> URL: https://issues.apache.org/jira/browse/HIVE-20025
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 3.0.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: Hive, hooks, pull-request-available
> Fix For: 4.0.0, 3.2.0
>
> Attachments: HIVE-20025.01-branch-3.patch, HIVE-20025.01.patch,
> HIVE-20025.02.patch, HIVE-20025.03.patch, HIVE-20025.04.patch
>
>
> Currently, HiveProtoLoggingHook write event data to hdfs. The number of files
> can grow to very large numbers.
> Since the files are created under a folder with Date being a part of the
> path, hive should have a way to clean up data older than a certain configured
> time / date. This can be a job that can run with as little frequency as just
> once a day.
> This time should be set to 1 week default. There should also be a sane upper
> bound of # of files so that when a large cluster generates a lot of files
> during a spike, we don't force the cluster fall over.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
