[ https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464096#comment-16464096 ]
Íñigo Goiri commented on HDFS-13522: ------------------------------------ Thanks [~csun] for the clarification; that makes sense. As a simplistic approach we could just ignore what the client does and let the Router decide what to use. However, this may not fit the model being envisioned by HDFS-12976. I would finish HDFS-12976 first and based on that we may go fancier and use some caller context or RPC header. Anyway, while doing HDFS-12976, just keep in mind this possible requirement. > 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 > Priority: Major > > 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