-
Niu Yawei authored
If blocking AST wasn't received by client before recovery, we need to scan the whole waiting lock list to send blocking ASTs after lock replay done, otherwise, client could be evicted unpurposely like following: - cl1 has a granted lock; - cl2 has a waiting lock, BL AST is sent but lost on a way; - failover, locks are replayed and applied on the server in the correct order; - waiting lock is just put to the resource, no new BL AST is re-sent, no timeout can happen for the granted lock on server, no timeout for the waiting lock on client; - cl2 will be hanging for a long time until cl1 will cancel its aged lock; may lead to cl2 eviction. Signed-off-by: Niu Yawei <yawei.niu@intel.com> Change-Id: I2a3fecf3b7fa79f96874d5ae21c599725334d9a5 Reviewed-on: https://review.whamcloud.com/24716 Reviewed-by: Vitaly Fertman <vitaly.fertman@seagate.com> Tested-by: Jenkins Tested-by: Maloo <hpdd-maloo@intel.com> Reviewed-by: Oleg Drokin <oleg.drokin@intel.com> Reviewed-by: Mike Pershin <mike.pershin@intel.com>
2ae4276e