[
https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539791#comment-17539791
]
Simbarashe Dzinamarira commented on HDFS-13522:
-----------------------------------------------
Hi [~xuzq_zander], thanks for the suggestion.
As of now I've split the PR into two
a) [https://github.com/apache/hadoop/pull/4311] : IPC changes for txid to flow
from clients through the routers, and to the namenodes.
b) [https://github.com/apache/hadoop/pull/4127] : Routers use this txid to do a
namespace specify msync and redirect calls to the observer.
I think most of the splits you suggested above would apply to (b). I'll think
further how to split (b) up to make reviews easier. However, I also would like
to avoid too many splits so that the smaller changes are testable and
"complete" in some sense.
> 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 10m
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
