You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/28 07:54:00 UTC
[jira] [Updated] (HDFS-16834) PoolAlignmentContext should not max poolLocalStateId with sharedGlobalStateId when sending requests to the namenode.
[ https://issues.apache.org/jira/browse/HDFS-16834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shilun Fan updated HDFS-16834:
------------------------------
Component/s: namnode
Target Version/s: 3.4.0
Affects Version/s: 3.4.0
> PoolAlignmentContext should not max poolLocalStateId with sharedGlobalStateId when sending requests to the namenode.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-16834
> URL: https://issues.apache.org/jira/browse/HDFS-16834
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namnode
> Affects Versions: 3.4.0
> Reporter: Simbarashe Dzinamarira
> Assignee: Simbarashe Dzinamarira
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> When sending requests to the namenode, we should only use the poolLocalStateId. Maxing it with the sharedGlobalStateId makes reads consistent across all clients using a router, which is not necessary and will lead to more waiting on the observer.
--
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