[
https://issues.apache.org/jira/browse/HADOOP-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667481#action_12667481
]
Raghu Angadi commented on HADOOP-5114:
--------------------------------------
HADOOP-4679 sets a 30 second timeout for the ServerSocket used by DataXceiver
thread. This server socket is a NIO socket. Tests seem to pass after commenting
out timeout setting. This seems to be yet another problem we are seeing with
Sun JDK's selectors. Blocking IO with JDK NIO sockets is pretty buggy and
unusable.. it works well only for the common use case of NIO : use a static
thread pool for non-blocking IO.
Couple of options :
* Use Hadoop's selector to wait on the socket ({{SocketIOWithTimeout}})
* May be a timeout is not necessary, if interrupting the thread wakes this
thread.
> A bunch of mapred unit tests are failing on Windows
> ---------------------------------------------------
>
> Key: HADOOP-5114
> URL: https://issues.apache.org/jira/browse/HADOOP-5114
> Project: Hadoop Core
> Issue Type: Test
> Components: mapred, test
> Affects Versions: 0.20.0
> Environment: Windows
> Reporter: Ramya R
> Priority: Minor
> Fix For: 0.20.0
>
>
> A bunch of unit tests are consistently failing when run on Windows. Below are
> a list of unit tests which are failing and the corresponding exceptions
> thrown:
> Exception: "java.net.ConnectException: Connection refused: no further
> information"
> Failing tests:
> * TestMiniMRMapRedDebugScript - testMapDebugScript
> * TestNoDefaultsJobConf - testNoDefaults
> * TestQueueManager - testAllEnabledACLForJobSubmission
> * TestCompressedEmptyMapOutputs -
> testMapReduceSortWithCompressedEmptyMapOutputs
> * TestJobInProgressListener - testJobQueueChanges
> * TestKillCompletedJob - testKillCompJob
> * TestMiniMRClasspath - testClassPath
> * TestMiniMRDFSCaching - testWithDFS
> * TestMiniMRWithDFSWithDistinctUsers - testDistinctUsers
> * TestSetupAndCleanupFailure - testWithDFS
> * TestDBJob - testRun
> * TestMiniMRWithDFS - testWithDFS
> * TestJobStatusPersistency - testNonPersistency
> * TestSpecialCharactersInOutputPath - testJobWithDFS
> * TestUserDefinedCounters - testMapReduceJob
> * TestDelegatingInputFormat - testSplitting
> * TestEmptyJobWithDFS - testEmptyJobWithDFS
> * TestJavaSerialization - testMapReduceJob
> * TestClusterMapReduceTestCase - testMapReduce
> Exception: java.lang.IllegalArgumentException: Pathname /<path> from <path>
> is not a valid DFS filename.
> Failing tests:
> * TestJobInProgress - testRunningTaskCount
> * TestJobQueueInformation - testJobQueues
> * TestJobTrackerRestart - testJobTrackerRestart
> Exception: java.io.IOException: Bad connect ack with firstBadLink
> 127.0.0.1:<port number>
> Failing tests:
> * TestJobSysDirWithDFS - testWithDFS
> * TestJobInProgress - testPendingMapTaskCount
> * TestMiniMRDFSSort - testMapReduceSort
> Exception: junit.framework.AssertionFailedError
> Failing tests:
> * TestMRServerPorts - testJobTrackerPorts
> * TestMRServerPorts - testTaskTrackerPorts
> * TestMiniMRTaskTempDir - testTaskTempDir
> Exception: java.io.IOException: Job failed!
> Failing tests:
> * TestMiniMRLocalFS - testWithLocal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
