hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1030) in unit tests, set ipc timeout in one place
Date Thu, 22 Feb 2007 18:55:06 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Doug Cutting updated HADOOP-1030:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

After reviewing with Nigel, I committed this.  With the increased timeout, unit tests completed
successfully twice in a row for me, which they never did yesterday.

Each 'ant clean test' run took 16.5 minutes.  I wonder if we could decrease that substantially
by merging several tests that start dfs or mapred daemons into a single test, so that daemons
are started and stopped fewer times?  We could even run test jobs in separate threads, so
that, e.g., while one test's reduce tasks are running another tests map tasks can run...

> in unit tests, set ipc timeout in one place
> -------------------------------------------
>                 Key: HADOOP-1030
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1030
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: test
>            Reporter: Doug Cutting
>         Assigned To: Doug Cutting
>            Priority: Minor
>             Fix For: 0.12.0
>         Attachments: HADOOP-1030.patch
> The unit test code currently decreases ipc.client.timeout in three different places in
order to speed the execution of unit tests (since daemon startup and shutdown time is related
to this value).  The value for unit tests should be set in only a single place.  Also, the
value used when testing should perhaps be increased from one second to two seconds, to make
tests more reliable.

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

View raw message