hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1883) Periodic cleanup of Hive History log files.
Date Wed, 05 Jan 2011 07:17:46 GMT

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

Carl Steinbach commented on HIVE-1883:
--------------------------------------

I sent this to the dev list earlier:

{quote}
Usually it's the Ops/IT staff that ends up managing things like a production HiveServer instance,
and in a UNIX shop I suspect that most of these folks are already going to be familiar with
using cron and logrotate (http://linuxcommand.org/man_pages/logrotate8.html) to manage the
logs produced by their other server systems. 

Building a log rotation feature into HiveServer defies this convention and will force people
to learn how to configure a new log rotation system specific to HiveServer. It also requires
us to write, debug, document and maintain code that isn't really necessary. I think the best
approach is to take advantage of what already exists by documenting Hive's logging behavior
in the Admin manual and providing a sample logrotate configuration file.
{quote}


> Periodic cleanup of Hive History log files.
> -------------------------------------------
>
>                 Key: HIVE-1883
>                 URL: https://issues.apache.org/jira/browse/HIVE-1883
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.6.0
>         Environment: Hive 0.6.0,  Hadoop 0.20.1
> SUSE Linux Enterprise Server 11 (i586)
> VERSION = 11
> PATCHLEVEL = 0
>            Reporter: Mohit Sikri
>
> After starting hive and running queries transaction history files are getting creating
in the /tmp/root folder.
> These files we should remove periodically(not all of them but) which are too old to represent
any significant information.
> Solution :-
> A scheduled timer task, which cleans up the log files older than the configured time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message