Mailing-List: contact user-help@jclouds.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@jclouds.apache.org
Received-SPF: pass (athena.apache.org: domain of yurykats@yahoo.com designates
 216.109.114.223 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com;
	b=uIr1OeckcvTJF4LMyjbFzdZIaCLBbd8yiuUf4YiJXMcUbPLPHGO8WfNqFKm+6Kt+VGRE+bHcDbnfw82aF8W+4Vl3yFeGV8iroA/yFFj+KV8jCL8O9Dd4jg0XBb95U/C2yDyWVlrhlwXyOqpW2ER/lWWJ6NA21TtpOY5wNPLRIwKvQcbRJrtf9YTzPEF/C+TtjTUzQHfaZIj+AZ1V3sgVUFS+J1uvqLDeQmkAzk2bnmwOlcGvmo/LVD/qweJ6JxlFvxyYiVyI/4ccR6kWtmos7SoorOY/Y3X8WlaBqJzrnQu1R/CeQMA/d7n3fLXmzPOm7Wd9j6+BDjdYh7LMLXYyXw==;
Message-ID: <544147B4.4020608@yahoo.com>
Date: Fri, 17 Oct 2014 12:45:40 -0400
From: Yury Kats <yurykats@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.7.1
MIME-Version: 1.0
To: user@jclouds.apache.org
Subject: Re: use exponential backoff on retry (was RE: JClouds BlobStore
 re-authentication
 when auth token expires)
References: 
 <8070c6efe74643e58385e56026d6356f@BLUPR0501MB897.namprd05.prod.outlook.com>
 <3918EC648ABC75468E8516B58EB8169C140147C6@ORD1EXD04.RACKSPACE.CORP>,<41b9406ce4e24ad2b32d6afe45389ced@BLUPR0501MB897.namprd05.prod.outlook.com>
 <3918EC648ABC75468E8516B58EB8169C140296F4@ORD1EXD04.RACKSPACE.CORP>
In-Reply-To: 
 <3918EC648ABC75468E8516B58EB8169C140296F4@ORD1EXD04.RACKSPACE.CORP>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit

CONNECTION_TIMEOUT applies to establishing a connection
SO_TIMEOUT applies to existing connection that is idle.

On 10/17/2014 12:32 PM, Zack Shoylev wrote:
> They are slightly different. I think the connection timeout only applies when initiating the connection to the remote host. I don't think they are additive.
> ________________________________________
> From: Daniel Hsueh [Daniel.Hsueh@evault.com]
> Sent: Wednesday, October 15, 2014 11:02 AM
> To: user@jclouds.apache.org
> Subject: RE: use exponential backoff on retry (was RE: JClouds BlobStore re-authentication when auth token expires)
> 
> Hello Zack,
> 
> Thank you for the explanation.
> 
> Could you clarify if, at each retry (after the delay), the SO_TIMEOUT (or CONNECTION_TIMEOUT) is waited-for as well?  And what is the difference between the SO_TIMEOUT and the CONNECTION_TIMEOUT?  (Comments in Constants.java say socket connection vs connection, code [e.g. HttpUtils] says "so" is socket open, and I can't seem to trace exactly where the values end up being used in practice.)
> 
> Thank you again.
> 
> Daniel Hsueh
> mailto:daniel.hsueh@evault.com tel:+1-905-287-2167
> 
> -----Original Message-----
> From: Zack Shoylev [mailto:zack.shoylev@RACKSPACE.COM]
> Sent: September 10, 2014 11:48 AM
> To: user@jclouds.apache.org
> Subject: RE: use exponential backoff on retry (was RE: JClouds BlobStore re-authentication when auth token expires)
> 
> Hi Daniel,
> 
> You should try testing with these Properties:
> 
> PROPERTY_SO_TIMEOUT - This will time-out the HTTP connection socket after the specified time. This specifies how long the client should wait before jclouds closes the connection and attempts to retry the HTTP call. I would suggest a value of 5 seconds.
> 
> PROPERTY_MAX_RETRIES - This specifies the maximum number of retries for the call that will be attempted by jclouds. Note that setting this to 0 will result in a single call. Setting this to 1 will retry once before failing.
> 
> PROPERTY_RETRY_DELAY_START - This specifies how long the exponential backoff waits between retries. The exponential backoff retry mechanism in jclouds will double this value after each retry.
> 
> I don't think you can set them differently for different operations, though.
> 
> -Zack
> ________________________________________
> From: Daniel Hsueh [Daniel.Hsueh@evault.com]
> Sent: Wednesday, September 10, 2014 8:38 AM
> To: user@jclouds.apache.org
> Subject: use exponential backoff on retry (was RE: JClouds BlobStore re-authentication when auth token expires)
> 
> Hello everyone,
> 
> Is there a way to configure the lengths of the delay in between retry attempts on auth, read, or write operations?
> 
> Thank you.
> 
> 
> Daniel Hsueh
> mailto:daniel.hsueh@evault.com tel:+1-905-287-2167
> 
> -----Original Message-----
> From: Daniel Hsueh
> Sent: September 2, 2014 11:38 AM
> To: 'user@jclouds.apache.org'
> Subject: RE: JClouds BlobStore re-authentication when auth token expires
> 
> [snip]
> 
> One thing I'd like to configure is some kind of exponential backoff when the auth retry fails.  IIRC, there are three RetryOnRenew classes, and they either retry 5 times, or retry 5 times with a fixed delay between the 2,3,4th attempts.  Is there a way to configure an increasing backoff?
> 
> Thanks!
> 
> 
> Daniel Hsueh
> mailto:daniel.hsueh@evault.com tel:+1-905-287-2167
> 
>