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-22514) HiveProtoLoggingHook might consume lots of memory
Date Wed, 20 Nov 2019 21:36:00 GMT

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

Hive QA commented on HIVE-22514:
--------------------------------



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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17710 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/19514/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/19514/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-19514/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12986336 - PreCommit-HIVE-Build

> HiveProtoLoggingHook might consume lots of memory
> -------------------------------------------------
>
>                 Key: HIVE-22514
>                 URL: https://issues.apache.org/jira/browse/HIVE-22514
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 4.0.0
>            Reporter: Attila Magyar
>            Assignee: Attila Magyar
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-22514.1.patch, Screen Shot 2019-11-18 at 2.19.24 PM.png
>
>
> HiveProtoLoggingHook uses a ScheduledThreadPoolExecutor to submit writer tasks and to
periodically handle rollover. The builtin ScheduledThreadPoolExecutor uses a unbounded queue
which cannot be replaced from the outside. If log events are generated at a very fast rate
this queue can grow large.
> !Screen Shot 2019-11-18 at 2.19.24 PM.png|width=650,height=101!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message