From cae4683971cca3bd19783ac69040307d1251d50b Mon Sep 17 00:00:00 2001 From: Frank Date: Tue, 16 May 2017 07:19:17 -0700 Subject: [PATCH] Make clearing of stale debug lock info independent of deleting map entry of lock itself. (#4353) This is believed to address issue #4337 where stale information for debug locks in shown. --- cmd/namespace-lock.go | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/cmd/namespace-lock.go b/cmd/namespace-lock.go index 75bce13ee..9aa470825 100644 --- a/cmd/namespace-lock.go +++ b/cmd/namespace-lock.go @@ -240,14 +240,12 @@ func (n *nsLockMap) ForceUnlock(volume, path string) { if _, found := n.lockMap[param]; found { // Remove lock from the map. delete(n.lockMap, param) - - // delete the lock state entry for given - // pair. - err := n.deleteLockInfoEntryForVolumePath(param) - if err != nil { - errorIf(err, "Failed to delete lock info entry") - } } + + // delete the lock state entry for given + // pair. Ignore error as there + // is no way to report it back + n.deleteLockInfoEntryForVolumePath(param) } // lockInstance - frontend/top-level interface for namespace locks.