[
https://issues.apache.org/jira/browse/HIVE-20247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559730#comment-16559730
]
Hive QA commented on HIVE-20247:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12933298/HIVE-20247.01.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/12897/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12897/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12897/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12933298/HIVE-20247.01.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: 12933298 - PreCommit-HIVE-Build
> cleanup issues in LLAP IO after cache OOM
> -----------------------------------------
>
> Key: HIVE-20247
> URL: https://issues.apache.org/jira/browse/HIVE-20247
> Project: Hive
> Issue Type: Bug
> Reporter: Prasanth Jayachandran
> Assignee: Sergey Shelukhin
> Priority: Major
> Attachments: HIVE-20247.01.patch, HIVE-20247.patch
>
>
> LLAP IO creates unallocated buffer objects inside the read-related data
> structures, then allocates them in bulk, then decompresses into them and
> increfs them.
> If allocate or decompress steps fail, it's hard for the higher-level cleanup
> to tell what the state of the buffers in the read-related structures is -
> they may be unallocated, allocated but not incref-ed, or incref-ed.
> Some cleanup paths only deal with the latter case, resulting in bugs.
> Moreover, currently allocator returns partial results on such error. The
> allocation should be all-or-nothing.
> This only happens on one path, others allocate and use buffers in a single
> place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
