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.

25.1.2 Disadvantages of Striping<br />

There are two disadvantages to striping which should deter you from choosing a<br />

default policy that stripes over all OSTs unless you really need it: increased overhead<br />

and increased risk.<br />

25.1.2.1 Increased Overhead<br />

Increased overhead comes in the form of extra network operations during common<br />

operations such as stat and unlink, and more locks. Even when these operations are<br />

performed in parallel, there is a big difference between doing 1 network operation<br />

and 100 operations.<br />

Increased overhead also comes in the form of server contention. Consider a cluster<br />

with 100 clients and 100 OSSs, each with one OST. If each file has exactly one object<br />

and the load is distributed evenly, there is no contention and the disks on each<br />

server can manage sequential I/O. If each file has 100 objects, then the clients all<br />

compete with one another for the attention of the servers, and the disks on each<br />

node seek in 100 different directions. In this case, there is needless contention.<br />

25.1.2.2 Increased Risk<br />

Increased risk is evident when you consider the example of striping each file across<br />

all servers. In this case, if any one OSS catches on-fire, a small part of every file is<br />

lost. By comparison, if each file has exactly one stripe, you lose fewer files, but you<br />

lose them in their entirety. Most users would rather lose some of their files entirely<br />

than all of their files partially.<br />

25.1.3 Stripe Size<br />

Choosing a stripe size is a small balancing act, but there are reasonable defaults. The<br />

stripe size must be a multiple of the page size. For safety, <strong>Lustre</strong>’s tools enforce a<br />

multiple of 64 KB (the maximum page size on ia64 and PPC64 nodes), so users on<br />

platforms with smaller pages do not accidentally create files which might cause<br />

problems for ia64 clients.<br />

Although you can create files with a stripe size of 64 KB, this is a poor choice.<br />

Practically, the smallest recommended stripe size is 512 KB because <strong>Lustre</strong> sends 1<br />

MB chunks over the network. This is a good amount of data to transfer at one time.<br />

Choosing a smaller stripe size may hinder the batching.<br />

Chapter 25 Striping and I/O Options 25-3

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

Saved successfully!

Ooh no, something went wrong!