I believe the read time out is per server. I think by default it will retry until it has tried to communicate with ever server, not just servers that have a copy of the object. So the factors that affect the total timeout are the read-timeout and retry-attempts.
-Dan On Tue, Aug 11, 2015 at 5:39 PM, Luke Shannon <[email protected]> wrote: > I am seeing a situation where a read is taking longer than the configured > read-timeout (ie: read-time out is 90 seconds, but some reads are taking 3 > times this). > > The read is from the java client on a partitioned region with one > redundant copy. > > Is the read time out measured per server that has a copy of the object? > What factors affect the read time out? >
