[Lustre-discuss] best practice for lustre clustre startup

[Kevin Van Maren]

My (personal) opinion:

Lustre clients should always start (mount) automatically.


Lustre servers should have their services started through heartbeat (or 
other HA package), if failover is possible (be sure to configure stonith).

If heartbeat starts automatically, do ensure auto-failback is NOT 
enabled: fail the resources back manually after you verify the rebooted 
server is healthy.
Whether heartbeat starts automatically seems to be a preference issue.

While unlikely, it is possible for an issue to cause Lustre to not start 
successfully, resulting in a node crash or other issue preventing a 
login.  So if it does start automatically you'll want to be prepared to 
reboot w/o Lustre (eg, single-user mode).

Kevin


Lisa Giacchetti wrote:
> Hello,
>  I have recently installed a lustre cluster which is in a test phase 
> now but will potentially be in 24x7 production if its accepted.
>  I would like input from the list on what the recommendations/best 
> practices are for configuration of a lustre cluster startup.
>  Is it advisable to have lustre on the various server pieces 
> (mgs/mdt/oss's) start automatically? If not why not?
>  If you try to start it and there is a very serious problem will it 
> abort the startup or just continue on blindly?
>
>  Again this is going to need to be a 24x7 service for a compute 
> facility that which has global access (ie someone is always
>  up and running something). We'd like  to be able to at least get the 
> service back up in an automated way if at all possible and then debug
>  problems when the support staff are awake/available.
>
>  Lisa Giacchetti
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>