hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20025) Clean-up of event files created by HiveProtoLoggingHook.
Date Thu, 05 Jul 2018 06:53:00 GMT

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

Hive QA commented on HIVE-20025:
--------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m 14s{color} | {color:red}
/data/hiveptest/logs/PreCommit-HIVE-Build-12396/patches/PreCommit-HIVE-Build-12396.patch does
not apply to master. Rebase required? Wrong Branch? See http://cwiki.apache.org/confluence/display/Hive/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Console output | http://104.198.109.242/logs//PreCommit-HIVE-Build-12396/yetus.txt |
| Powered by | Apache Yetus    http://yetus.apache.org |


This message was automatically generated.



> 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
>
>         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)

Mime
View raw message