23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

20.1.3.1 Configuring Adaptive Timeouts<br />

One of the goals of adaptive timeouts is to relieve users from having to tune the<br />

obd_timeout value. In general, obd_timeout should no longer need to be<br />

changed. However, there are several parameters related to adaptive timeouts that<br />

users can set. Keep in mind that in most situations, the default values will be usable.<br />

The following parameters can be set as module parameters in modprobe.conf or at<br />

runtime in /sys/module/ptlrpc. 1<br />

Note – This directory path may be different on some systems.<br />

Parameter<br />

Description<br />

at_min Sets the minimum adaptive timeout (in seconds). Default value is 0.<br />

The at_min parameter is the minimum processing time that a server<br />

will report. Clients base their timeouts on this value, but they do not<br />

use this value directly. If you experience cases in which, for unknown<br />

reasons, the adaptive timeout value is too short and clients time out<br />

their RPCs, then you can increase the at_min value to compensate<br />

for this. Ideally, users should leave at_min set to its default.<br />

at_max<br />

Sets the maximum adaptive timeout (in seconds). In <strong>Lustre</strong> <strong>1.6</strong>.5, the<br />

default value is 0 * . This setting causes adaptive timeouts to be<br />

disabled and the old fixed-timeout method (obd_timeout) to be<br />

used. The at_max parameter is an upper-limit on the service time<br />

estimate, and is used as a ‘failsafe’ in case of rogue/bad/buggy code<br />

that would lead to never-ending estimate increases. If at_max is<br />

reached, an RPC request is considered ‘broken’ and it should time<br />

out.<br />

NOTE: It is possible that slow hardware might validly cause the<br />

service estimate to increase beyond the default value of at_max. In<br />

this case, you should increase at_max to the maximum time you are<br />

willing to wait for an RPC completion.<br />

at_history<br />

Sets a time period (in seconds) within which adaptive timeouts<br />

remember the slowest event that occurred. Default value is 600.<br />

1. The specific sub-directory in ptlrpc containing the parameters is system dependent.<br />

20-6 <strong>Lustre</strong> <strong>1.6</strong> <strong>Operations</strong> <strong>Manual</strong> • September 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!