[
https://issues.apache.org/jira/browse/HDFS-17844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDFS-17844:
----------------------------------
Labels: patch pull-request-available (was: patch)
> Flaky test: testViewFsMultipleExportPoint may encounter race condition which
> leads to namenode ID collisions
> ------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17844
> URL: https://issues.apache.org/jira/browse/HDFS-17844
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode, test
> Reporter: Yakun Wang
> Priority: Major
> Labels: patch, pull-request-available
>
> There could be a race condition in namenode ID generation, causing ID
> collisions. However, the underlying collision detection logic is incorrect
> because it throws an error as long as the namenode ID exists, even if the URI
> is the same. Same namenode ID with same URI is safe. What needs to be
> detected is that different URIs resolve to the same namenode ID, which is a
> security problem.
> Error output:
> `[ERROR] Errors:
> [ERROR] TestExportsTable.testViewFsMultipleExportPoint:111 ยป FileSystem
> FS:viewfs, Namenode ID collision for path:/hdfs2 nnid:2130740544 uri being
> added:hdfs://localhost:34111/ existing uri:hdfs://localhost:34111/`
> Functions that are related to collision detection logic:
> # prepareAddressMap in
> hadoop/hadoop-hdfs-project/hadoop-hdfs-nfs/src/main/java/org/apache/hadoop/hdfs/nfs/nfs3/DFSClientCache.java
> # getNamenodeId in
> hadoop/hadoop-hdfs-project/hadoop-hdfs-nfs/src/main/java/org/apache/hadoop/hdfs/nfs/nfs3/Nfs3Utils.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
