Bug 1459850

Summary: [Tracker RHGS BZ#1463192] gluster-block: way to discard passive glfs obj from cache
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanna Kumar Kalever <prasanna.kalever>
Component: gluster-blockAssignee: Bhumika Goyal <bgoyal>
Status: CLOSED UPSTREAM QA Contact: Rahul Hinduja <rhinduja>
Severity: low Docs Contact:
Priority: low    
Version: cns-3.9CC: amukherj, atumball, hchiramm, nigoyal, pkarampu, rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-19 07:07:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1463192    
Bug Blocks: 1594112    

Description Prasanna Kumar Kalever 2017-06-08 10:53:53 UTC 
Description of problem:

Problem:
-------
While the glfs object of a volume is cached already,
if you delete the volume and create the volume with the same name, gluster-block currently uses the old volumes glfs object, which is not expected.

Why?
Because, current lru cache Hashing is based on volume name.

Solution:
--------
we would need to discard a cached object upon some number of failures or an option to explicitly discard an object from cache, or some equivalent policy
Comment 6 Prasanna Kumar Kalever 2018-09-21 09:27:57 UTC 
*** Bug 1594112 has been marked as a duplicate of this bug. ***
Comment 8 Amar Tumballi 2018-11-19 07:07:36 UTC 
> Why?
> Because, current lru cache Hashing is based on volume name.

Considering this is not expected to happen in a OCS scenario, would be great to take this to Upstream, and fix it there instead if valid. Also noticed that the other bug Niels said he is not able to reproduce the problem.