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

Hive QA commented on HIVE-21391:
--------------------------------



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

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

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

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

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: 12972750 - PreCommit-HIVE-Build

> LLAP: Pool of column vector buffers can cause memory pressure
> -------------------------------------------------------------
>
>                 Key: HIVE-21391
>                 URL: https://issues.apache.org/jira/browse/HIVE-21391
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>    Affects Versions: 4.0.0, 3.2.0
>            Reporter: Prasanth Jayachandran
>            Assignee: slim bouguerra
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21391.1.patch, HIVE-21391.2.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Where there are too many columns (in the order of 100s), with decimal, string 
> types the column vector pool of buffers created here 
> [https://github.com/apache/hive/blob/master/llap-server/src/java/org/apache/hadoop/hive/llap/io/decode/EncodedDataConsumer.java#L59]
>  can cause memory pressure. 
> Example:
> 128 (poolSize) * 300 (numCols) * 1024 (batchSize) * 80 (decimalSize) ~= 3GB
> The pool size keeps increasing when there is slow consumer but fast llap io 
> (SSDs) leading to GC pressure when all LLAP io threads read splits from same 
> table. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to