[
https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538548#comment-17538548
]
ZanderXu commented on HDFS-13522:
---------------------------------
Thanks [~simbadzina] , I'm very interested in this issues, and very happy to
do somethings for it.
This will be a relatively large PR, can we split it into small tasks and break
them one by one?
# Monitor the status of OBserver namenode and store it in state store
# Try to store the latest txid for each nameservice in memory
# Modify the logic of getNamenodesForNameservice(nsId) to support returning
different namenode list depending on whether it is ObserverRead or not
# Implement an MSync mechanism to try to get the latest txid for nameservice
# Forward ReadRequest to ObserverNamenode and WriteRequest to Active Namenode
# Modify the logic of invokemethod and try to correct the nn status in time.
[~elgoiri] I'm very happy to be back and continue to do some work for RBF. And
I'm very happy to contribute some practical experience to apache/Hadoop.:)
> RBF: Support observer node from Router-Based Federation
> -------------------------------------------------------
>
> Key: HDFS-13522
> URL: https://issues.apache.org/jira/browse/HDFS-13522
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: federation, namenode
> Reporter: Erik Krogen
> Assignee: Simbarashe Dzinamarira
> Priority: Major
> Labels: pull-request-available
> Attachments: HDFS-13522.001.patch, HDFS-13522.002.patch,
> HDFS-13522_WIP.patch, RBF_ Observer support.pdf, Router+Observer RPC
> clogging.png, ShortTerm-Routers+Observer.png
>
> Time Spent: 8h
> Remaining Estimate: 0h
>
> Changes will need to occur to the router to support the new observer node.
> One such change will be to make the router understand the observer state,
> e.g. {{FederationNamenodeServiceState}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
