[
https://issues.apache.org/jira/browse/HDDS-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JiangHua Zhu resolved HDDS-9748.
--------------------------------
Resolution: Duplicate
> When the command status is reported, the command set sent to the datanode is
> updated
> ------------------------------------------------------------------------------------
>
> Key: HDDS-9748
> URL: https://issues.apache.org/jira/browse/HDDS-9748
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Affects Versions: 1.3.0
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Labels: pull-request-available
>
> When SCM issues repeated deleteblocks commands to DN, we will get the
> following information in the DN's log:
> {code:java}
> 2023-11-21 15:57:16,711 [BlockDeletingService#5] WARN
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler: Missing delete
> block(Container = xxxx, Block = xxxxxx
> 2023-11-21 15:57:16,711 [BlockDeletingService#2] WARN
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler: Missing delete
> block(Container = xxxx, Block = xxxxxx
> 2023-11-21 15:57:16,711 [BlockDeletingService#4] WARN
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler: Missing delete
> block(Container = xxxx, Block = xxxxxx
> {code}
> This shouldn't happen because some block files have been deleted.
> There is a situation that will cause this phenomenon, that is,
> SCMBlockDeletingService has prepared the DeleteBlocksCommand set in advance,
> and the datanode has previously executed and deleted part of the block
> information. At this time, this batch of commands will be re-executed, and
> the above problem will occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
