<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11-06-06 6:06 AM, Galder Zamarreño wrote:
<blockquote
cite="mid:7454336F-B452-4382-8732-27E776FF3A8B@redhat.com"
type="cite">
<pre wrap="">Hmmm, I don't think the replication timeout has an effect during state transfer. Repl timeout is for individual rpc calls.
</pre>
</blockquote>
<br>
It is, *however* repl timeout can cause state transfer to timeout
due to locking of that processing lock in DistSync and that is why I
think state transfer timeout has to be at least as long as repl
timeout. <br>
<br>
<blockquote
cite="mid:7454336F-B452-4382-8732-27E776FF3A8B@redhat.com"
type="cite">
<pre wrap="">
Rehashing on the other hand is RPC based but the timeout is controlled by rehashRpcTimeout. Not sure what replTimeout has to do here.
</pre>
</blockquote>
<br>
You are right. One can explicitly set rehashRpcTimeout to less than
replTimeout and that is ok.<br>
<br>
<blockquote
cite="mid:7454336F-B452-4382-8732-27E776FF3A8B@redhat.com"
type="cite">
<pre wrap="">
Apart from that, another suggestion:
flushLockTimeout < shutDownTimeout (async) < <b class="moz-txt-star"><span class="moz-txt-tag">*</span>cacheStopTimeout<span class="moz-txt-tag">*</span></b>
</pre>
</blockquote>
<br>
Yep that one makes sense. Let's put this verification code in and
things will clear up further as we go along.<br>
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/ISPN-1153">https://issues.jboss.org/browse/ISPN-1153</a><br>
<br>
<br>
<br>
<br>
</body>
</html>