hive-issues mailing list archives

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


Hive QA commented on HIVE-20025:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12930097 - PreCommit-HIVE-Build

> Clean-up of event files created by HiveProtoLoggingHook.
> --------------------------------------------------------
>                 Key: HIVE-20025
>                 URL:
>             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.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

View raw message