[HDFS-4843] testDeleteBlockPool has a bug which makes it fail occasionally

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.4-alpha
• Component/s: federation

Environment

normal enviroment

• Assignee: Bharat Viswanadham
• Reporter: vincent cho
• Created: 23/May/13 02:47
• Updated: 13/Feb/18 18:20
• Resolved: 13/Feb/18 18:19

Description

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.

Issue Links

• duplicates: HDFS-5892 TestDeleteBlockPool fails in branch-2