[HDFS-16229] Remove the use of obsolete BLOCK_DELETION_INCREMENT

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 3.4.0
• Component/s: documentation, namenode
• Labels: pull-request-available
• Hadoop Flags: Reviewed
• Assignee: JiangHua Zhu
• Reporter: JiangHua Zhu
• Created: 17/Sep/21 07:56
• Updated: 18/Sep/21 05:37
• Resolved: 18/Sep/21 05:37

Description

As early as HDFS-13831, it was already
Removed the obsolete BLOCK_DELETION_INCREMENT, but ignored another use of BLOCK_DELETION_INCREMENT.
E.g:
/**

• From the given list, incrementally remove the blocks from blockManager
• Writelock is dropped and reacquired every BLOCK_DELETION_INCREMENT to
• ensure that other waiters on the lock can get in. See HDFS-2938
  *
• @param blocks
• An instance of {@link BlocksMapUpdateInfo}

  which contains a list

• of blocks that need to be removed from blocksMap
  */
  void removeBlocks(BlocksMapUpdateInfo blocks) { ...... }

Issue Links

• links to: GitHub Pull Request #3451