From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
Cc: Andy Adamson <andros@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: starting 90-second grace period
Date: Fri, 11 Dec 2009 13:20:43 -0500 [thread overview]
Message-ID: <1260555643.15701.4.camel@localhost> (raw)
In-Reply-To: <f5b5ebae0912111009i4c665758gab583a34dbaea0d9@mail.gmail.com>
On Fri, 2009-12-11 at 23:39 +0530, Tharindu Rukshan Bamunuarachchi
wrote:
> then why is it 90 by default ... is it RFC/Protocol requirement ?
The purpose of the grace period is to give the clients enough time to
notice that the server has rebooted, and to reclaim their existing locks
without danger of having somebody else steal the lock from them.
It is not a protocol requirement, but it is definitely a strongly
recommended feaature if you don't want to see corruption in your
mailbox/database/logfile/... that relies on those locks.
Trond
> On Fri, Dec 11, 2009 at 11:31 PM, Trond Myklebust
> <trond.myklebust@fys.uio.no> wrote:
> > On Fri, 2009-12-11 at 22:55 +0530, Tharindu Rukshan Bamunuarachchi
> > wrote:
> >> thankx a lot for the info.
> >>
> >> btw, if i set nfs4leasetime to ~10 seconds ... is there any negative effect ?
> >>
> >
> > You mean aside from the very likely event that your clients will lose
> > all their locks when the server reboots?
> >
> > Trond
> >
> >
>
>
>
next prev parent reply other threads:[~2009-12-11 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 11:00 starting 90-second grace period Tharindu Rukshan Bamunuarachchi
2009-12-11 17:08 ` Andy Adamson
2009-12-11 17:25 ` Tharindu Rukshan Bamunuarachchi
2009-12-11 18:01 ` Trond Myklebust
2009-12-11 18:09 ` Tharindu Rukshan Bamunuarachchi
2009-12-11 18:20 ` Trond Myklebust [this message]
2009-12-11 19:50 ` J. Bruce Fields
2009-12-11 20:09 ` Trond Myklebust
2009-12-11 20:12 ` J. Bruce Fields
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=1260555643.15701.4.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=andros@netapp.com \
--cc=btharindu@gmail.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