[jira] [Created] (HDFS-12983) Ozone: dozone: provide docker-compose file for cblock clusters

2018-01-03 Thread Elek, Marton (JIRA)
Elek, Marton created HDFS-12983:
---

 Summary: Ozone: dozone: provide docker-compose file for cblock 
clusters
 Key: HDFS-12983
 URL: https://issues.apache.org/jira/browse/HDFS-12983
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: ozone
Affects Versions: ozone
Reporter: Elek, Marton
Assignee: Elek, Marton


Since HDFS-12469 we have a docker compose file at dev-support/compose/ozone 
which makes it easy to start local ozone clusers with multiple datanodes.

In this patch I propose similar config file for the cblock/iscsi servers (jscsi 
+ cblock + scm + namenode + datanode) to make it easier to check the latest 
state.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org



[jira] [Created] (HDFS-12984) BlockPoolSlice can leak in a mini dfs cluster

2018-01-03 Thread Robert Joseph Evans (JIRA)
Robert Joseph Evans created HDFS-12984:
--

 Summary: BlockPoolSlice can leak in a mini dfs cluster
 Key: HDFS-12984
 URL: https://issues.apache.org/jira/browse/HDFS-12984
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 2.7.5
Reporter: Robert Joseph Evans


When running some unit tests for storm we found that we would occasionally get 
out of memory errors on the HDFS integration tests.

When I got a heap dump I found that the ShutdownHookManager was full of 
BlockPoolSlice$1 instances.  Which hold a reference to the BlockPoolSlice which 
then in turn holds a reference to the DataNode etc

It looks like when shutdown is called on the BlockPoolSlice there is no way to 
remove the shut down hook in because no reference to it is saved.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org



[jira] [Created] (HDFS-12985) NameNode crashes during restart after an OpenForWrite file present in the Snapshot got deleted

2018-01-03 Thread Manoj Govindassamy (JIRA)
Manoj Govindassamy created HDFS-12985:
-

 Summary: NameNode crashes during restart after an OpenForWrite 
file present in the Snapshot got deleted
 Key: HDFS-12985
 URL: https://issues.apache.org/jira/browse/HDFS-12985
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: hdfs
Affects Versions: 2.8.0
Reporter: Manoj Govindassamy
Assignee: Manoj Govindassamy


NameNode crashes repeatedly with NPE at the startup when trying to find the 
total number of under construction blocks. This crash happens after an open 
file, which was also part of a snapshot gets deleted along with the snapshot.

{noformat}
java.lang.NullPointerException
at 
org.apache.hadoop.hdfs.server.namenode.LeaseManager.getNumUnderConstructionBlocks(LeaseManager.java:144)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCompleteBlocksTotal(FSNamesystem.java:4456)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startCommonServices(FSNamesystem.java:1158)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.startCommonServices(NameNode.java:825)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:751)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:968)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:947)
at 
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1674)
at 
org.apache.hadoop.hdfs.MiniDFSCluster.restartNameNode(MiniDFSCluster.java:2110)
at 
org.apache.hadoop.hdfs.MiniDFSCluster.restartNameNode(MiniDFSCluster.java:2075)
at 
org.apache.hadoop.hdfs.server.namenode.snapshot.TestOpenFilesWithSnapshot.testSnapshotsForOpenFilesAndDeletion3(TestOpenFilesWithSnapshot.java:747)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
{noformat}






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org