You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sumit Agrawal (Jira)" <ji...@apache.org> on 2025/08/26 04:03:00 UTC

[jira] [Updated] (HDDS-13614) Create separate bounded executor for ClosePipelineCommandHandler and CreatePipelineCommandHandler

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

Sumit Agrawal updated HDDS-13614:
---------------------------------
        Parent: HDDS-13616
    Issue Type: Sub-task  (was: Bug)

> Create separate bounded executor for ClosePipelineCommandHandler and CreatePipelineCommandHandler
> -------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-13614
>                 URL: https://issues.apache.org/jira/browse/HDDS-13614
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Aswin Shakil
>            Priority: Critical
>
> Right now, we have a single unbounded executor for both ClosePipelineCommandHandler and CreatePipelineCommandHandler. If either of these handlers is slow, it will cause a backlog on the entire thread's queue. It will later result in OutOfMemoryError as the queue size keeps on increasing and crash the DN.
> We have a "hdds.datanode.command.queue.limit", but we don't use it for this executor. We should make this queue bounded and we should also have separate executors for both so that one handler doesn't become a bottleneck for the other. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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