[ https://issues.apache.org/jira/browse/HDDS-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-2449: -------------------------------- Affects Version/s: (was: 0.5.0) 0.6.0 Labels: TriagePending (was: ) > Delete block command should use a thread pool > --------------------------------------------- > > Key: HDDS-2449 > URL: https://issues.apache.org/jira/browse/HDDS-2449 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Datanode > Affects Versions: 0.6.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.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org