[
https://issues.apache.org/jira/browse/HIVE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633049#comment-16633049
]
Hive QA commented on HIVE-20649:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12941770/HIVE-20649.2.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14128/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14128/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14128/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12941770/HIVE-20649.2.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12941770 - PreCommit-HIVE-Build
> LLAP aware memory manager for Orc writers
> -----------------------------------------
>
> Key: HIVE-20649
> URL: https://issues.apache.org/jira/browse/HIVE-20649
> Project: Hive
> Issue Type: Bug
> Affects Versions: 4.0.0, 3.2.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Priority: Major
> Attachments: HIVE-20649.1.patch, HIVE-20649.2.patch
>
>
> ORC writer has its own memory manager that assumes memory usage or memory
> available based on JVM heap (MemoryMX bean). This works on tez container mode
> execution model but not in LLAP where container sizes (and Xmx) are typically
> high and there are multiple executors per LLAP daemon. This custom memory
> manager should be aware of memory bounds per executor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
