Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
The current code places bl_ast lock callbacks at the end of the global BL callback queue. This is bad because it causes urgent requests from the server to wait behind non-urgent cleanup tasks to keep lru_size at the right level.
This can lead to evictions if there is a large queue of items in the global queue so the callback is not serviced in a timely manner.
Put bl_ast callbacks on the priority queue so they do not wait behind the background traffic.
Attachments
Issue Links
Activity
Fix Version/s | New: Lustre 2.15.4 [ 16190 ] |
Link | New: This issue is related to DDN-3298 [ DDN-3298 ] |
Description |
Original:
The current code places bl_ast lock callbacks at the end of
the global BL callback queue. This is bad because it causes urgent requests from the server to wait behind non-urgent cleanup tasks to keep lru_size at the right level. This can lead to evictions if there is a large queue of items in the global queue so the callback is not serviced in a timely manner. Put bl_ast callbacks on the priority queue so they do not wait behind the background traffic. |
New:
The current code places bl_ast lock callbacks at the end of the global BL callback queue. This is bad because it causes urgent requests from the server to wait behind non-urgent cleanup tasks to keep lru_size at the right level.
This can lead to evictions if there is a large queue of items in the global queue so the callback is not serviced in a timely manner. Put bl_ast callbacks on the priority queue so they do not wait behind the background traffic. |
Fix Version/s | New: Lustre 2.16.0 [ 15190 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link | New: This issue is related to DDN-3192 [ DDN-3192 ] |
Link | New: This issue is related to DDN-2795 [ DDN-2795 ] |