[#LU-4942] lock callback timeout is not per-export

[LU-4942] lock callback timeout is not per-export Created: 22/Apr/14 Updated: 12/Mar/19 Resolved: 30/Oct/14
Status:	Resolved
Project:	Lustre
Component/s:	None
Affects Version/s:	None
Fix Version/s:	Lustre 2.7.0

Type:

Bug

Priority:

Critical

Reporter:

Vitaly Fertman

Assignee:

Oleg Drokin

Resolution:

Fixed

Votes:

Labels:

patch

Issue Links:

Related
is related to	~~LU-4579~~	Timeout system horribly broken	Resolved
is related to	LU-12064	Adaptive timeout at_min adjustment & ...	Reopened

Severity:

Rank (Obsolete):

13659

Description

The gathered lock callback timeout statistics is common for the whole cluster, what means it does not handle slow clients properly what leads to client evictions.

(moving my work from ~~LU-4579~~ to a separate ticker)

Comments

Comment by Vitaly Fertman [ 22/Apr/14 ]

CODE: http://review.whamcloud.com/#/c/9336/

Comment by Peter Jones [ 22/Apr/14 ]

Thanks Vitaly!

Comment by Peter Jones [ 30/Oct/14 ]

Landed for 2.7

Generated at Sat Feb 10 01:47:11 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.

[LU-4942] lock callback timeout is not per-export Created: 22/Apr/14 Updated: 12/Mar/19 Resolved: 30/Oct/14