[Lustre-devel] question about ldlm_server_glimpse_ast

Oleg Drokin oleg.drokin at oracle.com
Fri Apr 30 14:14:07 PDT 2010


On Apr 30, 2010, at 5:07 PM, John Hammond wrote:

> Are there any nonobvious ramifications of changing ldlm_timeout?  I noticed that it was set to 20 seconds (except for MDS's?) in 1.8.2. Also there is some suspect looking logic in obd_config.c and elsewhere to keep it from being set too high relative to obd_timeout:
>    if (ldlm_timeout >= obd_timeout)
>        ldlm_timeout = max(obd_timeout / 3, 1U);
> Does this mean that ldlm_timeout should not exceed 1/3 of obd_timeout?

ldlm_timeout should not be set too high, because if a client that holds a lock dies
this is for how long nobody will be able to get a conflicting lock.
Of course if your network might delay packets (roundtrip) for more than
ldlm_timeout, then you need to lift the limit.
1/3 is there so that if your network delay is potentially this big (and you do not
use AT), there should be enough time to do some processing still and then send a reply
to the client (obd_timeout is used for the client to determine when the reply should
come) before the client times out that request.

Also see the comment from Cory, that if you use AT it is all not controlled
by at_min setting instead and then is dynamically adjusted as the system detects your
network latency.


More information about the lustre-devel mailing list