[LU-17428] reduce default value for lru_max_age to 300s Created: 16/Jan/24 Updated: 16/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | Andreas Dilger |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
The default value for lru_max_age is currently 3900s (3900000 msec), or 1h5m. For most systems and use cases, this is far too long and can lead to clients holding on to locks that they don't need and may cause issues for other clients if those clients holding the LDLM locks have any network issues and the server lock callback RPCs are slow. It may also cause issues with the LRU, if clients hold on to locks only used once for a long time and potentially evict more important locks sooner, though more work is still needed to the DLM LRU algorithm in LU-11509. We regularly tune ldlm.namespaces.*.lru_max_age=300s on large clusters, and it makes sense to change this to be the default. |
| Comments |
| Comment by Gerrit Updater [ 16/Jan/24 ] |
|
"Andreas Dilger <adilger@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53682 |
| Comment by Gerrit Updater [ 16/Jan/24 ] |
|
"Andreas Dilger <adilger@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/doc/manual/+/53684 |
| Comment by Gerrit Updater [ 16/Jan/24 ] |
|
"Andreas Dilger <adilger@whamcloud.com>" merged in patch https://review.whamcloud.com/c/doc/manual/+/53684/ |