shine does not apply tunings in expected order
Opened this issue · 3 comments
Some Lustre tunings require to apply their values in a specific order.
For instance, the llite max_read_ahead_per_file_mb parameter must be set after the max_read_ahead_mb one, otherwise it will be reset to the same value as max_read_ahead_mb.
However, shine does not apply these tunings in a deterministic order (changing the order in which they appear in the tuning.conf file will not change the order they are applied).
As a consequence, it is not possible to apply the above settings using the tuning.conf file.
Reported by: fsr-atos
- status: new --> accepted
Original comment by: degremont
Indeed Shine applies tunings in tuning.conf in parallel. This speeds up start phase dramatically. There is no way to workaround this in Shine for now. We should think about it.
For your problème, you can use lctl conf_param or set_param -P to workaround this.
Original comment by: degremont
- Milestone: 1.5 --> 1.6
Original comment by: degremont