You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Takanobu Asanuma (Jira)" <ji...@apache.org> on 2023/02/23 07:55:00 UTC
[jira] [Commented] (HADOOP-18345) Enhance client protocol to propagate last seen state IDs for multiple nameservices.
[ https://issues.apache.org/jira/browse/HADOOP-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692548#comment-17692548 ]
Takanobu Asanuma commented on HADOOP-18345:
-------------------------------------------
It is only in trunk. I corrected the fixed versions.
> Enhance client protocol to propagate last seen state IDs for multiple nameservices.
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-18345
> URL: https://issues.apache.org/jira/browse/HADOOP-18345
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Simbarashe Dzinamarira
> Assignee: Simbarashe Dzinamarira
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The RPCHeader in the client protocol currently contains a single value to indicate the last seen state ID for a namenode.
> {noformat}
> optional int64 stateId = 8; // The last seen Global State ID
> {noformat}
> When there are multiple namenodes, such as in router based federation, the headers need to carry the state IDs for each of these nameservices that are part of the federation.
> This change is a prerequisite for HDFS-13522: RBF: Support observer node from Router-Based Federation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org