You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2011/01/25 07:09:43 UTC
[jira] Updated: (WHIRR-207) Handle curl timeouts better
[ https://issues.apache.org/jira/browse/WHIRR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated WHIRR-207:
------------------------------
Summary: Handle curl timeouts better (was: Handle wget timeouts better)
It is actually curl, sorry for the wrong title (corrected). The scripts already have a retry:
{code}
curl="curl --retry 3 --silent --show-error --fail"
for i in `seq 1 3`;
do
$curl -O $hbase_tar_url
$curl -O $hbase_tar_url.md5
if md5sum -c $hbase_tar_md5_file; then
break;
else
rm -f $hbase_tar_file $hbase_tar_md5_file
fi
done
{code}
Are these errors that actually do the retry loop? And if so, should the be a
{code}
if [ $i -gt 1 ]; then
sleep 10;
fi
{code}
or some such to wait before the retry? When to give up entirely?
> Handle curl timeouts better
> ---------------------------
>
> Key: WHIRR-207
> URL: https://issues.apache.org/jira/browse/WHIRR-207
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Lars George
>
> I have had that happen before and now again. We need to handle this better:
> {code}
> + for i in '`seq 1 3`'
> + curl --retry 3 --silent --show-error --fail -O http://archive.apache.org/dist/hbase/hbase-0.20.6/hbase-0.20.6.tar.gz
> curl: (18) transfer closed with 12646997 bytes remaining to read
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.