public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: Fail over more quickly on connect errors
Date: Mon, 19 Apr 2010 19:35:40 -0400	[thread overview]
Message-ID: <4BCCE8CC.3050102@oracle.com> (raw)
In-Reply-To: <1271456992.3098.20.camel@localhost.localdomain>

On 04/16/2010 06:29 PM, Trond Myklebust wrote:
> On Fri, 2010-04-16 at 16:47 -0400, Trond Myklebust wrote:
>> We should not allow soft tasks to wait for longer than the major timeout
>> period when waiting for a reconnect to occur.
>>
>> Signed-off-by: Trond Myklebust<Trond.Myklebust@netapp.com>
>> ---
>>   net/sunrpc/xprt.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/net/sunrpc/xprt.c b/net/sunrpc/xprt.c
>> index c71d835..01449a3 100644
>> --- a/net/sunrpc/xprt.c
>> +++ b/net/sunrpc/xprt.c
>> @@ -710,7 +710,7 @@ void xprt_connect(struct rpc_task *task)
>>   		if (task->tk_rqstp)
>>   			task->tk_rqstp->rq_bytes_sent = 0;
>>
>> -		task->tk_timeout = xprt->connect_timeout;
>> +		task->tk_timeout = min(req->rq_timeout, xprt->connect_timeout);
>                                           ^^^ task->tk_rqstp->rq_timeout
>
> Apologies. I though I had tested that...
>
>> 		rpc_sleep_on(&xprt->pending, task, xprt_connect_status);
>>
>>   		if (test_bit(XPRT_CLOSING,&xprt->state))

I tested this series of patches with soft mounts, and RPC requests now 
fail, after the timeout period, if the client can't reconnect.

I also observed appropriate exponential back-off behavior as the client 
attempts to reconnect.  I would suggest one more patch to reduce the 
reestablish timeout maximum to 30 seconds.

For the series:

Reviewed-by: Chuck Lever <chuck.lever@oracle.com>

   and/or

Tested-by: Chuck Lever <chuck.lever@oracle.com>

-- 
chuck[dot]lever[at]oracle[dot]com

      reply	other threads:[~2010-04-19 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 20:47 [PATCH] SUNRPC: Clean up xprt_release() Trond Myklebust
2010-04-16 20:47 ` [PATCH] SUNRPC: Cleanup - make rpc_new_task() call rpc_release_calldata on failure Trond Myklebust
2010-04-16 20:47   ` [PATCH] SUNRPC: Move the test for XPRT_CONNECTING into xprt_connect() Trond Myklebust
2010-04-16 20:47     ` [PATCH] SUNRPC: Fail over more quickly on connect errors Trond Myklebust
2010-04-16 20:47       ` [PATCH] NFSv4: Allow attribute caching with 'noac' mounts if client holds a delegation Trond Myklebust
2010-04-16 20:47         ` [PATCH] NFSv4: Clean up the NFSv4 setclientid operation Trond Myklebust
2010-04-16 22:29       ` [PATCH] SUNRPC: Fail over more quickly on connect errors Trond Myklebust
2010-04-19 23:35         ` Chuck Lever [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BCCE8CC.3050102@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox