[
https://issues.apache.org/jira/browse/HIVE-15508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796132#comment-15796132
]
Sergey Shelukhin commented on HIVE-15508:
-----------------------------------------
It seems like a hard problem in Java world. Should we just move any significant
allocations to memory manager and buffers (GBY, PTF, etc.), and assume nobody
allocates anything else unless they are running UDFs? :)
> 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
>
> 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
(v6.3.4#6332)
