[ https://issues.apache.org/jira/browse/HDFS-13212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391628#comment-16391628 ]
Íñigo Goiri commented on HDFS-13212: ------------------------------------ After a deeper look, the part that concerns me is the following: {code} 485 // Add the default location and test location cache 486 assertEquals("null->/testlocationcache", 487 mountTable.getDestinationForPath("/testlocationcache").toString()); {code} The fact that is returning null is weird. My guess is that the default location is {{null}} but we should have some other as default and verify that once we remove the entry, we go to that default. So I would make say 0 the default and then assert we point there. > RBF: Fix router location cache issue > ------------------------------------ > > Key: HDFS-13212 > URL: https://issues.apache.org/jira/browse/HDFS-13212 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: federation, hdfs > Reporter: Weiwei Wu > Assignee: Weiwei Wu > Priority: Major > Attachments: HDFS-13212-001.patch, HDFS-13212-002.patch, > HDFS-13212-003.patch, HDFS-13212-004.patch, HDFS-13212-005.patch, > HDFS-13212-006.patch, HDFS-13212-007.patch > > > The MountTableResolver refreshEntries function have a bug when add a new > mount table entry which already have location cache. The old location cache > will never be invalid until this mount point change again. > Need to invalid the location cache when add the mount table entries. -- 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