Bug 1459850 - gluster-block: way to discard passive glfs obj from cache
gluster-block: way to discard passive glfs obj from cache
Status: ASSIGNED
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gluster-block (Show other bugs)
3.3
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Prasanna Kumar Kalever
Rahul Hinduja
3.3.0-defer
: ZStream
Depends On: 1463192
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-08 06:53 EDT by Prasanna Kumar Kalever
Modified: 2017-06-28 07:27 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Prasanna Kumar Kalever 2017-06-08 06:53:53 EDT
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

Note You need to log in before you can comment on or make changes to this bug.