[
https://issues.apache.org/jira/browse/HDFS-17935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088493#comment-18088493
]
ASF GitHub Bot commented on HDFS-17935:
---------------------------------------
kokonguyen191 opened a new pull request, #8548:
URL: https://github.com/apache/hadoop/pull/8548
### Description of PR
Most router traffic are reads, and currently all traffic to a namespace is
handled by one same executor, so high observer load can increase competition
for active ops. It would be beneficial to split the handler pools into 2
separate sets, one for active, one for observer.
Added a simple unit test (LLM-gen for skeleton then rewrote) to count how
many calls are proxied through which executor. Contains content generated by
Codex/ChatGPT-5.5.
### How was this patch tested?
UT. Have been running on production environment for months.
### AI Tooling
If an AI tool was used:
- [x] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [x] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> [ARR] Separate router async handlers for active and observer
> ------------------------------------------------------------
>
> Key: HDFS-17935
> URL: https://issues.apache.org/jira/browse/HDFS-17935
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs, rbf
> Reporter: Felix N
> Assignee: Felix N
> Priority: Minor
>
> Most router traffic are reads, and currently all traffic to a namespace is
> handled by one same executor, so high observer load can increase competition
> for active ops. It would be beneficial to split the handler pools into 2
> separate sets, one for active, one for observer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
