[FLINK-13985] Use unsafe memory for managed memory.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.10.0
• Component/s: Runtime / Task
• Labels: pull-request-available
• Assignee: Andrey Zagrebin
• Reporter: Xintong Song
• Created: 06/Sep/19 02:54
• Updated: 18/Dec/20 02:33
• Resolved: 22/Oct/19 16:50

Description

• Allocate memory with Unsafe.allocateMemory
  • MemoryManager

Implement this issue in common code paths for the legacy / new mode. This should only affect the GC behavior.

Issue Links

• causes: FLINK-14522 Adjust GC Cleaner for unsafe memory and Java 11
• causes: FLINK-14894 HybridOffHeapUnsafeMemorySegmentTest#testByteBufferWrap failed on Travis
• causes: FLINK-20663 Managed memory may not be released in time when operators use managed memory frequently
• causes: FLINK-15094 Warning about using private constructor of java.nio.DirectByteBuffer in Java 11
• relates to: FLINK-15758 Investigate potential out-of-memory problems due to managed unsafe memory allocation
• links to: GitHub Pull Request #9747