hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vincent cho (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-4843) testDeleteBlockPool has a bug which makes it fail occasionally
Date Thu, 23 May 2013 02:49:19 GMT
vincent cho created HDFS-4843:

             Summary: 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

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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message