[
https://issues.apache.org/jira/browse/HADOOP-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611965#action_12611965
]
Steve Loughran commented on HADOOP-3694:
----------------------------------------
Following up on Greg's suggestion, I dont think it is jetty. Whenever I kill
-QUIT a test case I see my machine stuck in Inet6addressImpl.getHostByAddr()
I've seen this on 3 different test cases so far: different tests, all in
getHostName(). This is on my machine on a managed network, with IPv6 as well as
IPv4.
[junit] Running org.apache.hadoop.hdfs.TestAbandonBlock
[junit] ===== FULL THREAD DUMP ===============
[junit] Wed Jul 9 11:02:07 2008
[junit] BEA JRockit(R) R27.4.0-90-89592-1.6.0_02-20070928-1715-linux-x86_64
[junit] "Main Thread" id=1 idx=0x4 tid=23092 prio=5 alive, in native
[junit] at
java/net/Inet6AddressImpl.getHostByAddr([B)Ljava/lang/String;(Native Method)
[junit] at java/net/InetAddress$1.getHostByAddr(InetAddress.java:853)
[junit] at
java/net/InetAddress.getHostFromNameService(InetAddress.java:533)
[junit] at java/net/InetAddress.getHostName(InetAddress.java:476)
[junit] at java/net/InetAddress.getHostName(InetAddress.java:448)
[junit] at
java/net/InetSocketAddress.getHostName(InetSocketAddress.java:210)
[junit] at
org/apache/hadoop/hdfs/server/datanode/DataNode.startDataNode(DataNode.java:414)
[junit] at
org/apache/hadoop/hdfs/server/datanode/DataNode.start(DataNode.java:226)
[junit] at org/apache/hadoop/util/Service.deploy(Service.java:261)
[junit] at
org/apache/hadoop/hdfs/server/datanode/DataNode.makeInstance(DataNode.java:3062)
[junit] at
org/apache/hadoop/hdfs/server/datanode/DataNode.instantiateDataNode(DataNode.java:3013)
[junit] at
org/apache/hadoop/hdfs/MiniDFSCluster.startDataNodes(MiniDFSCluster.java:411)
[junit] ^-- Holding lock: org/apache/hadoop/hdfs/[EMAIL PROTECTED] lock]
[junit] at
org/apache/hadoop/hdfs/MiniDFSCluster.<init>(MiniDFSCluster.java:277)
[junit] at
org/apache/hadoop/hdfs/MiniDFSCluster.<init>(MiniDFSCluster.java:123)
[junit] at
org/apache/hadoop/hdfs/TestAbandonBlock.testAbandonBlock(TestAbandonBlock.java:38)
TestCLI is taking its time for a different reason; there's a sleep in teardown()
[junit] "Main Thread" id=1 idx=0x4 tid=11685 prio=5 alive, in native,
sleeping, native_waiting
[junit] at java/lang/Thread.sleep(J)V(Native Method)
[junit] at org/apache/hadoop/cli/TestCLI.tearDown(TestCLI.java:137)
Can someone on a different machine
1. run the tests
2. bring up top in a different window to see what is the Java process ID for a
test case
3. kill -QUIT that process and see where we are blocking.
If it is networking, it may behave differently for different users, and
machines with IPv6 suffer more.
> if MiniDFS startup time could be improved, testing time would be reduced
> ------------------------------------------------------------------------
>
> Key: HADOOP-3694
> URL: https://issues.apache.org/jira/browse/HADOOP-3694
> Project: Hadoop Core
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
>
> Its taking me 140 minutes to run a test build; looking into the test results
> its the 20s startup delay of every MiniDFS cluster that is slowing things
> down. If we could find out why it is taking so long and cut it down, every
> test case that relied on a cluster would be speeded up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
