[
https://issues.apache.org/jira/browse/HIVE-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945840#comment-15945840
]
Sergey Shelukhin edited comment on HIVE-16318 at 3/28/17 8:08 PM:
------------------------------------------------------------------
[~sseth] [~thejas] [~gopalv] [~jdere]
Both fixes that we've discussed in the meeting.
The metadata cache is basically split into a separate memory limit with
separate cache policy. This should "just work", I'll test it in the cluster
later today. The limit is set as 10% of total cache memory.
was (Author: sershe):
[~sseth] [~thejas] [~gopalv] [~jdere]
Both fixes that we've discussed in the meeting
> LLAP cache: address some issues in 2.2/2.3
> ------------------------------------------
>
> Key: HIVE-16318
> URL: https://issues.apache.org/jira/browse/HIVE-16318
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-16318.patch
>
>
> We've run into HIVE-16233 and HIVE-15665 and given that 2.2 and 2.3 releases
> are approaching we are going to add workarounds for them, and then commit the
> above patches and revert the workarounds as soon as we can.
> Unfortunately this will result in cache wasting some memory on some datasets,
> but the alternatives, when they are encountered (usually only on large
> datasets), are worse.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
