hive-dev 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-6314) The logging (progress reporting) is too verbose
Date Tue, 28 Jan 2014 19:38:43 GMT

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

Hive QA commented on HIVE-6314:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12625533/HIVE-6314.1.patch.txt

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4932 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_auto_sortmerge_join_16
{noformat}

Test results: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1070/testReport
Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1070/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12625533

> The logging (progress reporting) is too verbose
> -----------------------------------------------
>
>                 Key: HIVE-6314
>                 URL: https://issues.apache.org/jira/browse/HIVE-6314
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sam
>            Assignee: Navis
>              Labels: logger
>         Attachments: HIVE-6314.1.patch.txt
>
>
> The progress report is issued every second even when no progress have been made:
> {code}
> 2014-01-27 10:35:55,209 Stage-1 map = 100%,  reduce = 0%, Cumulative CPU 6.68 sec
> 2014-01-27 10:35:56,678 Stage-1 map = 100%,  reduce = 0%, Cumulative CPU 6.68 sec
> 2014-01-27 10:35:59,344 Stage-1 map = 100%,  reduce = 0%, Cumulative CPU 6.68 sec
> 2014-01-27 10:36:01,268 Stage-1 map = 100%,  reduce = 100%, Cumulative CPU 8.67 sec
> 2014-01-27 10:36:03,149 Stage-1 map = 100%,  reduce = 100%, Cumulative CPU 8.67 sec
> {code}
> This pollutes the logs and the screen, and people do not appreciate it as much as the
designers might have thought ([http://stackoverflow.com/questions/20849289/how-do-i-limit-log-verbosity-of-hive],
[http://stackoverflow.com/questions/14121543/controlling-the-level-of-verbosity-in-hive]).
> It would be nice to be able to control the level of verbosity (but *not* by the {{-v}}
switch!):
> # Make sure that the progress report is only issued where there is something new to report;
or
> # Remove all the progress messages; or
> # Make sure that progress is reported only every X sec (instead of every 1 second)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message