[ https://issues.apache.org/jira/browse/HIVE-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641274#comment-16641274 ]
Hive QA commented on HIVE-20649: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12942717/HIVE-20649.3.patch {color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified. {color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 15065 tests executed *Failed tests:* {noformat} org.apache.hadoop.hive.ql.io.orc.TestOrcFile.testLlapAwareMemoryManager[1] (batchId=291) org.apache.hive.jdbc.TestJdbcWithMiniLlapArrow.testKillQuery (batchId=252) {noformat} Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/14301/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14301/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14301/ 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 Tests exited with: TestsFailedException: 2 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 12942717 - 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 > > > 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)