You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/09/17 16:30:07 UTC
[jira] [Resolved] (WHIRR-655) installations can time out on slow
networks -timeout needs to be configurable
[ https://issues.apache.org/jira/browse/WHIRR-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved WHIRR-655.
----------------------------------
Resolution: Invalid
-timeouts are caused by something else -dfsadmin blocking until NN not coming out of Safe mode. Comments in whirr.log about read timeouts are irrelevant
> installations can time out on slow networks -timeout needs to be configurable
> -----------------------------------------------------------------------------
>
> Key: WHIRR-655
> URL: https://issues.apache.org/jira/browse/WHIRR-655
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.9.0
> Environment: cable connection; first yum install of a set of artifacts hosted on S3
> Reporter: Steve Loughran
> Priority: Minor
>
> Downloading RPMs from a yum repo over a slow link can take so long that scripts start to time out & your systems are left in an indeterminate state. It ought to be possible to specify timeouts on a per-cluster basis.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira