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.

13.2.2 Supported Upgrade Paths<br />

The following <strong>Lustre</strong> upgrade paths are supported.<br />

Entire file system or individual servers / clients<br />

■<br />

■<br />

■<br />

Servers can undergo a "rolling upgrade", in which individual servers (or their<br />

failover partners) and clients are upgraded one at a time and restarted, so that the<br />

file system never goes down. This type of upgrade limits your ability to change<br />

certain parameters.<br />

The entire file system can be shut down, and all servers and clients upgraded at<br />

once.<br />

Any combination of the above two paths.<br />

Interoperability between the nodes<br />

This describes the interoperability between clients, OSTs, and MDTs.<br />

Clients<br />

■ Old live clients can continue to communicate with old/new/mixed servers.<br />

■<br />

■<br />

Old clients can start up using old/new/mixed servers.<br />

New clients can start up using old/new/mixed servers (use old mount format for<br />

old MDT).<br />

OSTs<br />

■ New clients/MDTs can continue to communicate with old OSTs.<br />

■ New OSTs can only be started after the MGS has been started (typically this<br />

means "after the MDT has been upgraded.")<br />

MDTs<br />

■<br />

■<br />

■<br />

New clients can communicate with old MDTs.<br />

New co-located MGS/MDTs can be started at any point.<br />

New non-MGS MDTs can be started after the MGS starts.<br />

Note – The limitation with interoperability is that old clients cannot mount a file<br />

system which was created by a new MDT.<br />

Chapter 13 Upgrading <strong>Lustre</strong> 13-3

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

Saved successfully!

Ooh no, something went wrong!