[HBASE-23374] ExclusiveMemHFileBlock’s allocator should not be hardcoded as ByteBuffAllocator.HEAP

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.3.0
• Hadoop Flags: Reviewed
• Assignee: chenxu
• Reporter: chenxu
• Created: 06/Dec/19 03:07
• Updated: 07/Apr/20 20:46
• Resolved: 25/Dec/19 20:44

Description

ExclusiveMemHFileBlock's constructor looks like this:

ExclusiveMemHFileBlock(BlockType blockType, int onDiskSizeWithoutHeader,
      int uncompressedSizeWithoutHeader, long prevBlockOffset, ByteBuff buf, boolean fillHeader,
      long offset, int nextBlockOnDiskSize, int onDiskDataSizeWithHeader,
      HFileContext fileContext) {
    super(blockType, onDiskSizeWithoutHeader, uncompressedSizeWithoutHeader, prevBlockOffset, buf,
        fillHeader, offset, nextBlockOnDiskSize, onDiskDataSizeWithHeader, fileContext,
        ByteBuffAllocator.HEAP);
  }

After HBASE-22802, ExclusiveMemHFileBlock’s data may be allocated through the BB pool, so it’s allocator should not be hard coded as ByteBuffAllocator.HEAP

Issue Links

• links to: GitHub Pull Request #905