[
https://issues.apache.org/jira/browse/HADOOP-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683683#action_12683683
]
Steve Loughran commented on HADOOP-5517:
----------------------------------------
ipc.Server.stop() is synchronized, so this should be impossible. Yet it has
happened. Maybe the interrupt() operations that take place in the block do
something to release the locks. This is going to be a tricky one to deal with.
It could just be a quirk of the test bench, with all the different bits of the
cluster running in the same JVM. Or it could be a problem that can occur in the
wild.
What waits for these notifications?
> IllegalMonitorStateException in DataNode shutdown
> -------------------------------------------------
>
> Key: HADOOP-5517
> URL: https://issues.apache.org/jira/browse/HADOOP-5517
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Amareshwari Sriramadasu
>
> This was observed in one of the hudson runs,
> org.apache.hadoop.mapred.TestBadRecords.testBadMapRed failed with following
> exception trace:
> {noformat}
> java.lang.IllegalMonitorStateException
> at java.lang.Object.notifyAll(Native Method)
> at org.apache.hadoop.ipc.Server.stop(Server.java:1110)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.shutdown(DataNode.java:576)
> at
> org.apache.hadoop.hdfs.MiniDFSCluster.shutdownDataNodes(MiniDFSCluster.java:569)
> at
> org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:553)
> at
> org.apache.hadoop.mapred.ClusterMapReduceTestCase.stopCluster(ClusterMapReduceTestCase.java:129)
> at
> org.apache.hadoop.mapred.ClusterMapReduceTestCase.tearDown(ClusterMapReduceTestCase.java:140)
> {noformat}
> More logs @
> http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/94/testReport/org.apache.hadoop.mapred/TestBadRecords/testBadMapRed/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
