[
https://issues.apache.org/jira/browse/HIVE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649302#comment-16649302
]
Hive QA commented on HIVE-20649:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12943707/HIVE-20649.6.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15082 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14434/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14434/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14434/
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: 12943707 - 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,
> HIVE-20649.3.patch, HIVE-20649.4.patch, HIVE-20649.5.patch, HIVE-20649.6.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)
