ipc unit tests fail due to connection errors
--------------------------------------------

                 Key: HADOOP-2974
                 URL: https://issues.apache.org/jira/browse/HADOOP-2974
             Project: Hadoop Core
          Issue Type: Bug
          Components: ipc
    Affects Versions: 0.17.0
         Environment: windows
            Reporter: Mukund Madhugiri
            Assignee: Robert Chansler
            Priority: Blocker
             Fix For: 0.17.0


ipc unit tests fail due to connection errors:

Failing tests:
org.apache.hadoop.ipc.TestIPC.unknown
org.apache.hadoop.ipc.TestIPCServerResponder.unknown
org.apache.hadoop.ipc.TestRPC.testSlowRpc
org.apache.hadoop.ipc.TestRPC.testCalls

Changes:
# HADOOP-2346. Utilities to support timeout while writing to sockets. DFSClient 
and DataNode sockets have 10min write timeout.
# HADOOP-2906. Add an OutputFormat capable of using keys, values, and config 
params to map records to different output files.
# HADOOP-2756. NPE in DFSClient while closing DFSOutputStreams under load.
# HADOOP-2934. The namenode was encountreing a NPE while loading leases from 
the fsimage. Fixed.
# HADOOP-2925. Fix HOD to create mapred system directory using a naming 
convention that will avoid clashes in multi-user shared cluster scenario.
# HADOOP-2911. Make the information printed by the HOD allocate and info 
commands less verbose and clearer.
# HADOOP-2883. Write failures and data corruptions on HDFS files. The write 
timeout is back to what it was on 0.15 release. Also, the datnodes flushes the 
block file buffered output stream before sending a positive ack for the packet 
back to the client.
# HADOOP-2861. INCOMPATIBLE CHANGE. Improve the user interface for the HOD 
commands. Command line structure has changed.

Error logs:
 [junit] Running org.apache.hadoop.ipc.TestIPC
    [junit] 2008-03-07 10:50:04,291 INFO  metrics.RpcMetrics 
(RpcMetrics.java:<init>(53)) - Initializing RPC Metrics with hostName=0, 
port=4785
    [junit] 2008-03-07 10:50:04,354 INFO  ipc.Server (Server.java:run(443)) - 
IPC Server Responder: starting
    [junit] 2008-03-07 10:50:04,369 INFO  ipc.Server (Server.java:run(303)) - 
IPC Server listener on 4785: starting
    [junit] 2008-03-07 10:50:04,369 INFO  ipc.Server (Server.java:run(861)) - 
IPC Server handler 0 on 4785: starting
    [junit] 2008-03-07 10:50:04,369 INFO  ipc.Server (Server.java:run(861)) - 
IPC Server handler 1 on 4785: starting
    [junit] 2008-03-07 10:50:04,369 INFO  ipc.Server (Server.java:run(861)) - 
IPC Server handler 2 on 4785: starting
    [junit] 2008-03-07 10:50:04,432 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 1 time(s).
    [junit] 2008-03-07 10:50:04,432 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 1 time(s).
    [junit] 2008-03-07 10:50:05,432 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 2 time(s).
    [junit] 2008-03-07 10:50:05,432 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 2 time(s).
    [junit] 2008-03-07 10:50:06,432 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 3 time(s).
    [junit] 2008-03-07 10:50:06,432 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 3 time(s).
    [junit] 2008-03-07 10:50:07,433 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 4 time(s).
    [junit] 2008-03-07 10:50:07,433 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 4 time(s).
    [junit] 2008-03-07 10:50:08,433 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 5 time(s).
    [junit] 2008-03-07 10:50:08,433 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 5 time(s).
    [junit] 2008-03-07 10:50:09,433 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 6 time(s).
    [junit] 2008-03-07 10:50:09,433 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 6 time(s).
    [junit] 2008-03-07 10:50:10,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 7 time(s).
    [junit] 2008-03-07 10:50:10,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 7 time(s).
    [junit] 2008-03-07 10:50:11,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 8 time(s).
    [junit] 2008-03-07 10:50:11,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 8 time(s).
    [junit] 2008-03-07 10:50:12,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 9 time(s).
    [junit] 2008-03-07 10:50:12,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 9 time(s).
    [junit] 2008-03-07 10:50:13,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 10 time(s).
    [junit] 2008-03-07 10:50:13,434 INFO  ipc.Client 
(Client.java:setupIOstreams(177)) - Retrying connect to server: /0.0.0.0:4785. 
Already tried 10 time(s).
    [junit] 2008-03-07 10:50:14,435 FATAL ipc.TestIPC (TestIPC.java:run(92)) - 
Caught: java.net.BindException: Cannot assign requested address: no further 
information
    [junit] 2008-03-07 10:50:14,435 FATAL ipc.TestIPC (TestIPC.java:run(92)) - 
Caught: java.net.BindException: Cannot assign requested address: no further 
information



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to