[
https://issues.apache.org/jira/browse/HDFS-16834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simbarashe Dzinamarira updated HDFS-16834:
------------------------------------------
Description: 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. (was: When sending requests to the namenode, we
should also use the Pool's stateID. Maxing it with the sharedGlobalStateId
makes reads consistent across all clients using a router. This is not
necessarily and could lead to more waiting on the observer.)
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
