[
https://issues.apache.org/jira/browse/HDFS-15108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013380#comment-17013380
]
Hudson commented on HDFS-15108:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17852 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17852/])
HDFS-15108. RBF: MembershipNamenodeResolver should invalidate cache
(ayushsaxena: rev 7b62409ace165603ee137561d7d75b1e742ed9a2)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/resolver/MembershipNamenodeResolver.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs-rbf/src/test/java/org/apache/hadoop/hdfs/server/federation/resolver/TestNamenodeResolver.java
> 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
> Fix For: 3.3.0
>
> Attachments: HDFS-15108-01.patch, HDFS-15108-02.patch,
> HDFS-15108-03.patch, HDFS-15108-04.patch, HDFS-15108-05.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: [email protected]
For additional commands, e-mail: [email protected]
