[ 
https://issues.apache.org/jira/browse/HADOOP-18345?focusedWorklogId=792381&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-792381
 ]

ASF GitHub Bot logged work on HADOOP-18345:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jul/22 22:50
            Start Date: 18/Jul/22 22:50
    Worklog Time Spent: 10m 
      Work Description: goiri commented on PR #4584:
URL: https://github.com/apache/hadoop/pull/4584#issuecomment-1188405280

   @ZanderXu please take a look at:
   https://issues.apache.org/jira/browse/HDFS-13522
   @simbadzina added a design doc too:
   
https://issues.apache.org/jira/secure/attachment/13046815/observer_reads_in_rbf_proposal_simbadzina_v1.pdf




Issue Time Tracking
-------------------

    Worklog Id:     (was: 792381)
    Time Spent: 1h  (was: 50m)

> 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
>          Time Spent: 1h
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to