You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Mukul Kumar Singh (Jira)" <ji...@apache.org> on 2019/12/18 03:54:00 UTC

[jira] [Updated] (HDDS-2448) Delete container command should used a thread pool

     [ https://issues.apache.org/jira/browse/HDDS-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mukul Kumar Singh updated HDDS-2448:
------------------------------------
    Fix Version/s: 0.5.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

This is already merged in the github PR. Resolving this jira as well.

> Delete container command should used a thread pool
> --------------------------------------------------
>
>                 Key: HDDS-2448
>                 URL: https://issues.apache.org/jira/browse/HDDS-2448
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>    Affects Versions: 0.5.0
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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