[jira] [Updated] (HDFS-17651) [ARR] Async handler executor isolation.

["Xiaoqiao He (Jira)" <ji...@apache.org>]

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

Xiaoqiao He updated HDFS-17651:
-------------------------------
    Description: 
The main purpose of this PR is to isolate each nameservice by letting each nameservice has its own async handler thread pool.
Think below situation:
When a downstream nameserivce ns1 has poor performance, the threads in async handler thread pool will be occupied adding calls to the ns1's Connection#calls. There will be no available threads to handle normal nameservice's rpc request asynchronously. Therefore, it is better to isolate the async handler thread pool of different nameservices.

> [ARR] Async handler executor isolation.
> ---------------------------------------
>
>                 Key: HDFS-17651
>                 URL: https://issues.apache.org/jira/browse/HDFS-17651
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: farmmamba
>            Assignee: farmmamba
>            Priority: Major
>              Labels: pull-request-available
>
> The main purpose of this PR is to isolate each nameservice by letting each nameservice has its own async handler thread pool.
> Think below situation:
> When a downstream nameserivce ns1 has poor performance, the threads in async handler thread pool will be occupied adding calls to the ns1's Connection#calls. There will be no available threads to handle normal nameservice's rpc request asynchronously. Therefore, it is better to isolate the async handler thread pool of different nameservices.



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

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