You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apply performance tuning when mounting FSx for Lustre
We have to create a custom mount helper to better accommodate parameters persistence across instance reboot and head node instance type update.
lctl set_param commands have to be executed after the file systems are mounted and do not persist over instance reboot. The FSx document advises to use a boot cron job to set the parameter after reboot. However, a boot cron job is not compatible with our use case because FSx Lustre file systems are mounted upon first access instead of instance reboot (see code (https://github.com/aws/aws-parallelcluster-cookbook/blob/develop/cookbooks/aws-parallelcluster-config/resources/manage_fsx.rb#L60)). Therefore, we have to create a custom mount helper (see mount man page (https://linux.die.net/man/8/mount)):
Q: Are these operations affect the client FSx configuration or the server configuration?
A: Client only.
Q: How it will work if a customer mounts FSx manually?
A: If they use lustre as the mount type, the performance tuning will not be applied.
Q: How do customers know they will have to use the mount helper?
A: They will have to read ParallelCluster official doc.
Signed-off-by: Hanwen <[email protected]>
0 commit comments