[jira] [Resolved] (HDFS-16229) Remove the use of obsolete BLOCK_DELETION_INCREMENT

["Ayush Saxena (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-16229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ayush Saxena resolved HDFS-16229.
---------------------------------
    Fix Version/s: 3.4.0
     Hadoop Flags: Reviewed
       Resolution: Fixed

> Remove the use of obsolete BLOCK_DELETION_INCREMENT
> ---------------------------------------------------
>
>                 Key: HDFS-16229
>                 URL: https://issues.apache.org/jira/browse/HDFS-16229
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation, namenode
>            Reporter: JiangHua Zhu
>            Assignee: JiangHua Zhu
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 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) {
>    ......
> }



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org