[
https://issues.apache.org/jira/browse/HDFS-16834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZanderXu resolved HDFS-16834.
-----------------------------
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
> 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
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
