[ https://issues.apache.org/jira/browse/HDFS-15108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012223#comment-17012223 ]
Íñigo Goiri commented on HDFS-15108: ------------------------------------ Can we do a better cleanup of the cache and just remove what we need instead of everything? Otherwise, I'm fine with this approach even though is a little invasive. Let's create a method to do String to InetSocketAddress. In there we can cache rpcAddr.indexOf(":") and probably do a split. > RBF: MembershipNamenodeResolver should invalidate cache incase of active > namenode update > ---------------------------------------------------------------------------------------- > > Key: HDFS-15108 > URL: https://issues.apache.org/jira/browse/HDFS-15108 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Ayush Saxena > Assignee: Ayush Saxena > Priority: Major > Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch > > > If a failover happens, {{namenodeResolver.updateActiveNamenode(nsId, > address);}} is called, but this doesn't invalidates the cache, so as the next > time the correct active is fetched. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org