23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

20.2.9 Locking<br />

/proc/fs/lustre/ldlm/ldlm/namespaces//lru_size<br />

The lru_size parameter is used to control the number of client-side locks in an LRU<br />

queue. LRU size is dynamic, based on load. This optimizes the number of locks<br />

available to nodes that have different workloads (e.g., login/build nodes vs.<br />

compute nodes vs. backup nodes).<br />

The total number of locks available is a function of the server’s RAM. The maximum<br />

is 50 locks/MB. If there is too much memory pressure, then the LRU size is shrunk.<br />

■ To enable automatic LRU sizing, set the lru_size parameter to 0. In this case, the<br />

lru_size parameter shows the current number of locks being used on the export.<br />

■ To specify a maximum number of locks, set the lru_size parameter to a value > 0<br />

(former numbers are okay, 100 * CPU_NR). We recommend that you only increase<br />

the LRU size on a few login nodes where users access the file system interactively.<br />

The following command can be used to clear the LRU on a single client, and as a<br />

result flush client cache, without changing the lru_size value:<br />

$ lctl set_param ldlm.namespaces..lru_size=clear<br />

If you shrink the LRU size below the number of existing unused locks, then the<br />

unused locks are canceled immediately. Use echo clear to cancel all locks without<br />

changing the value.<br />

20-24 <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!