
|
If you were logged in you would be able to see more operations.
|
|
|
|
The second or later time a name node comes up in the sf-hadoop tests, it fails with a locked directory error. This would imply another namenode instance holds the lock
|
|
Description
|
The second or later time a name node comes up in the sf-hadoop tests, it fails with a locked directory error. This would imply another namenode instance holds the lock |
Show » |
|
at org.smartfrog.services.hadoop.core.SFHadoopException.forward(SFHadoopException.java:203)
at org.smartfrog.services.hadoop.components.cluster.HadoopServiceImpl.innerDeploy(HadoopServiceImpl.java:300)
at org.smartfrog.services.hadoop.components.cluster.HadoopServiceImpl.access$000(HadoopServiceImpl.java:41)
at org.smartfrog.services.hadoop.components.cluster.HadoopServiceImpl$ServiceDeployerThread.execute(HadoopServiceImpl.java:377)
at org.smartfrog.sfcore.utils.SmartFrogThread.run(SmartFrogThread.java:279)
at org.smartfrog.sfcore.utils.WorkflowThread.run(WorkflowThread.java:117)
Caused by: java.io.IOException: Cannot lock storage /tmp/hadoop/dfs/name. The directory is already locked.
at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.lock(Storage.java:511)
at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:1062)
at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:1085)
at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:83)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:310)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:289)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:164)
at org.apache.hadoop.hdfs.server.namenode.NameNode.innerStart(NameNode.java:225)
at org.apache.hadoop.util.Service.start(Service.java:183)
at org.smartfrog.services.hadoop.components.cluster.HadoopServiceImpl.innerDeploy(HadoopServiceImpl.java:294)