Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <361465737.1233009000120.JavaMail.jira@brutus>
Date: Mon, 26 Jan 2009 14:30:00 -0800 (PST)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5114) A bunch of mapred unit tests are
 failing on Windows
In-Reply-To: <29920304.1232698139658.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667470#action_12667470 ] 

Raghu Angadi commented on HADOOP-5114:
--------------------------------------

>From the log that Kostantin gave me, it it not a connect() related problem. The DataNode Xceiver thread fails to accept connections with this exception :

{noformat}[...]    DataXceiveServer: Exiting due to:java.nio.channels.ClosedSelectorException
    [junit]     at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:66)
    [junit]     at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:88)
    [junit]     at sun.nio.ch.Util.releaseTemporarySelector(Util.java:135)
    [junit]     at sun.nio.ch.ServerSocketAdaptor.accept(ServerSocketAdaptor.java:120)
    [junit]     at org.apache.hadoop.hdfs.server.datanode.DataXceiverServer.run(DataXceiverServer.java:130)
    [junit]     at java.lang.Thread.run(Thread.java:619)
{noformat}

Because of this, later attempts by clients to connect to DN fails with "connection refused" exceptions.

> 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.