[
https://issues.apache.org/jira/browse/HADOOP-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666690#action_12666690
]
Doug Cutting commented on HADOOP-5114:
--------------------------------------
> I think its important to make sure the client side all works on windows,
> regardless of what your server architecture is.
If we only supported Windows clients, how would we support debugging on Windows
LocalRunner? MiniDFS and MiniMR (i.e., running a cluster in a single JVM)?
Debugging with multiple JVMs (a.k.a "pseudo-distributed") catches lots of
problems that are hard to catch with a single JVM, e.g., relative path and
classpath issues.
Also, if we wish to support client-side only, then we'd need to test that
automatically, which might mean we:
- start a standalone cluster on a linux host
- start a virtual windows box on that linux host that runs client tests
against the linux-based cluster.
> 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.
