[ https://issues.apache.org/jira/browse/HADOOP-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-18345. ------------------------------------ Fix Version/s: 3.4.0 3.3.9 Resolution: Fixed > 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, 3.3.9 > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org