[ https://issues.apache.org/jira/browse/HDFS-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham resolved HDFS-4843. -------------------------------------- Resolution: Duplicate Assignee: Bharat Viswanadham > testDeleteBlockPool has a bug which makes it fail occasionally > -------------------------------------------------------------- > > Key: HDFS-4843 > URL: https://issues.apache.org/jira/browse/HDFS-4843 > Project: Hadoop HDFS > Issue Type: Bug > Components: federation > Affects Versions: 2.0.4-alpha > Environment: normal enviroment > Reporter: vincent cho > Assignee: Bharat Viswanadham > Priority: Major > > int the test case "testDeleteBlockPool" : > first we set "DFSConfigKeys.DFS_NAMESERVICES" as > "namesServerId1,namesServerId2", but after a cluster was built, the > nameservice are set as "ns1,ns2" because the code set a default value for > them when we new one cluster. > then we refresh namenode with the nameservice set as "namesServerId2" . so we > will add a new nameservice named "namesServerId2" and remove the two old > nameservices. because "ns2" and "namesServerId2" have the same bpid, so when > the add thread run faster than the remove process, the bpByBlockPoolId in > BlockPoolManager will be empty so that it fails when create a new file or > path. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org