[
https://issues.apache.org/jira/browse/HDDS-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650529#comment-17650529
]
mingchao zhao commented on HDDS-2449:
-------------------------------------
Ozone 1.3.0 had been released and we currently have more than 600 open issues
targeted for 1.3.0. I am moving the target field to 1.4.0.
If there is anything needs to be discussed about the Target Version, Please
reach out to me via Apache email or Slack.
> Delete block command should use a thread pool
> ---------------------------------------------
>
> Key: HDDS-2449
> URL: https://issues.apache.org/jira/browse/HDDS-2449
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Affects Versions: 1.0.0
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: TriagePending
>
> The datanode receives commands over the heartbeat and queues all commands on
> a single queue in StateContext.commandQueue. Inside DatanodeStateMachine a
> single thread is used to process this queue (started by initCommandHander
> thread) and it passes each command to a ‘handler’. Each command type has its
> own handler.
> The delete block command immediately executes the command on the thread used
> to process the command queue. Therefore if the delete is slow for some reason
> (it must access disk, so this is possible) it could cause other commands to
> backup.
> This should be changed to use a threadpool to queue the deleteBlock command,
> in a similar way to ReplicateContainerCommand.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
