From: Cory Spitz <spitzcor@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] question about ldlm_server_glimpse_ast
Date: Fri, 30 Apr 2010 14:25:54 -0500 [thread overview]
Message-ID: <4BDB2EC2.7030104@cray.com> (raw)
In-Reply-To: <B1CC7901-3220-4BD6-89EE-B37C825DCB03@oracle.com>
Hello.
Increasing ldlm_timeout has no effect whatsoever if adaptive timeouts are
enabled. See bug 22569. I suggest that you tune up at_min instead.
Thanks,
-Cory
Oleg Drokin wrote:
> Hello!
>
> On Apr 30, 2010, at 9:00 AM, John Hammond wrote:
>> I tested a patch which set rq_no_resend = 0 for glimpses, and found that
>> clients only had about 6 seconds to reply before eviction. Since
>> eviction creates the possibility for data loss, a 6 second timeout was
>> deemed too short for production. (With the patch applied, it was easy
>> for me to create cases where data was indeed lost.) I was also able to
>
> Please note that the 6 second timeout is in fact common ldlm_timeout and it's
> not just glimpses that are bound by this value.
> any ldlm callbacks are required to reply withing this time, so if your
> network can have delays of more then this much, you need to consider
> increasing ldlm_timeout value (/proc/sys/lustre/ldlm_timeout).
> On the other hand if you have a packet loss issue, even if
> resending of glimpse ASTs would be present, we don't currently resend
> other ASTs so the situation still has a potential for evictions
> with subsequent possible data loss.
>
> Bye,
> Oleg
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>
next prev parent reply other threads:[~2010-04-30 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 2:59 [Lustre-devel] question about ldlm_server_glimpse_ast Jeremy Filizetti
2010-04-30 13:00 ` John Hammond
2010-04-30 18:44 ` Oleg Drokin
2010-04-30 19:25 ` Cory Spitz [this message]
2010-04-30 21:07 ` John Hammond
2010-04-30 21:14 ` Oleg Drokin
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=4BDB2EC2.7030104@cray.com \
--to=spitzcor@cray.com \
--cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.