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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/11/08 19:14:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17630577#comment-17630577 ]
ASF GitHub Bot commented on HDFS-16834:
---------------------------------------
simbadzina opened a new pull request, #5121:
URL: https://github.com/apache/hadoop/pull/5121
HDFS-16834: Removes request stateID consistency constraint between clients in different connection pools.
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g., 'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
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.
### How was this patch tested?
Tests in TestObserverWithRouter still pass.
### For code changes:
- [x ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org