[
https://issues.apache.org/jira/browse/HIVE-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999739#comment-16999739
]
Syed Shameerur Rahman commented on HIVE-15508:
----------------------------------------------
As mentioned "each executors can have different memory usage" as there is no
guard on the memory usage of each executor, Can LLAP daemon go OOM anytime?
[~prasanth_j] [~sershe] [~sseth]
> LLAP: Find better way to track memory usage per executor
> --------------------------------------------------------
>
> Key: HIVE-15508
> URL: https://issues.apache.org/jira/browse/HIVE-15508
> Project: Hive
> Issue Type: Bug
> Components: llap
> Affects Versions: 2.2.0
> Reporter: Prasanth Jayachandran
> Priority: Major
>
> Many hive operators make runtime decisions based on memory usage. For getting
> the memory usage, Runtime.getUsed() or MemoryMXBean methods are used. This
> works fine for MR or Tez but for LLAP the entire memory is shared among
> multiple executors and each executors can have different memory usage.
> HIVE-15503 assumes the memory usage is shared across all executors. If we
> track memory usage per executor, also memory usage by on-heap cache better
> decisions can be made by the operators.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
