[ https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837545#comment-16837545 ]
Ayush Saxena commented on HDFS-13522: ------------------------------------- Thanx Everyone for the discussion!!! I guess we should focus primarily on SBN here and can discuss the quee stuff majorly itself at HDFS-14090. [~crh] had a quick look at the proposed design posted. * Is the major idea behind spliting the router into two half is as like the Read-Only appears to be as an Observer and the Write one as Active to the end Client, so as to use existing SBN client can connect to RBF similarly as it connects to a normal NS? * I guess if we intend to change this way, we should ensure the older setup where routers served all stays intact. May be the Write ones stays be regular Router(present one) serving all requests(both Read/Write) and the Read-Only may come up as a additions. * Well if I am catching it correct, How do you plan to handle the State Id stuff for the client when it connects through Router. In case of Single NS, that was pretty straight forward, but router connects to multiple NS. Not sure if here too you plan to handle at router(msync for every call) Whether this approach would have any edge over the one already up by Surendra. Neither the intent to make the client process exactly same as the present SBN scenario shall stay. Since for Read your own write client doesn't require an msync. Would be great If you could share some more details and plans regarding it.:) > 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: Chao Sun > Priority: Major > Attachments: HDFS-13522.001.patch, Router+Observer RPC clogging.png, > ShortTerm-Routers+Observer.png > > > 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org