[
https://issues.apache.org/jira/browse/HADOOP-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486436
]
Doug Cutting commented on HADOOP-1198:
--------------------------------------
It was 1 second for many months, until I increased it to 2 seconds in
HADOOP-1030, a bit over a month ago, so that things would run better on the
heavily loaded Solaris box where we run nightly benchmarks.
How often do you see timeouts with {1,2,5,10} seconds? On what kind of machine?
Related is, how much difference does changing this have on total unit test
time? It used to make a big difference, but now that many daemons are stopped
with Thread.interrupt() instead of waiting for the timeout interval, total unit
test time may not be so sensitive to this parameter. If it's not, then we
might even just leave it at the default.
> ipc.client.timeout of 2000ms for test cases seems too small; causes too many
> timeouts and leads to hung test cases
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-1198
> URL: https://issues.apache.org/jira/browse/HADOOP-1198
> Project: Hadoop
> Issue Type: Bug
> Components: test
> Affects Versions: 0.12.2
> Reporter: Arun C Murthy
> Assigned To: Arun C Murthy
> Fix For: 0.13.0
>
> Attachments: HADOOP-1198_20070403_1.patch
>
>
> We should increase the timeout slightly... what do other think? 5000ms?
> 10000ms?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
