[
https://issues.apache.org/jira/browse/HDFS-12354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141419#comment-16141419
]
Yiqun Lin commented on HDFS-12354:
----------------------------------
It's a good point, [~cheersyang]. I am thinking one another way, every time we
can get top n containers sorted by under deletion blocks num? Is this a better
way than just get a shuffle list? This way can also ensure we will not get the
same container list but it depends on querying the deleted blocks within
interval time. How do you think?
> Ozone: Shuffle container list for datanode BlockDeletingService
> ---------------------------------------------------------------
>
> Key: HDFS-12354
> URL: https://issues.apache.org/jira/browse/HDFS-12354
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, ozone
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
>
> {{BlockDeletingService}} is a per-datanode container block deleting service
> takes in charge of the "real" deletion of ozone blocks. It spawns a worker
> thread per container and delete blocks/chunks from disk as background
> threads. The number of threads currently is throttled by
> {{ozone.block.deleting.container.limit.per.interval}}, but there is a
> potential problem. Containers are sorted so it always fetch same of
> containers, we need to fix this by creating an API in
> {{ContainerManagerImpl}} to get a shuffled list of containers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
