You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2019/11/11 13:05:07 UTC

[GitHub] [hadoop-ozone] sodonnel opened a new pull request #142: HDDS-2448 Delete container command should used a thread pool

sodonnel opened a new pull request #142: HDDS-2448 Delete container command should used a thread pool
URL: https://github.com/apache/hadoop-ozone/pull/142
 
 
   …r than on the main commandDispatcher thread
   
   ## What changes were proposed in this pull request?
   
   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 container 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 deleteContainer command, in a similar way to ReplicateContainerCommand.
   
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-2448
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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