Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.2.0, 4.0.0
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- requires
-
ORC-409 Changes for extending MemoryManagerImpl
- Closed