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 "Simbarashe Dzinamarira (Jira)" <ji...@apache.org> on 2022/11/08 18:37: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 ]

Simbarashe Dzinamarira updated HDFS-16834:
------------------------------------------
    Summary: PoolAlignmentContext should not max poolLocalStateId with sharedGlobalStateId when sending requests to the namenode.  (was: PoolAlignmentContext should not max poolStateId with sharedGlobalStateId when sending requests)

> 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 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.



--
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