Bug 1459850 - [Tracker RHGS BZ#1463192] gluster-block: way to discard passive glfs obj from cache
Summary: [Tracker RHGS BZ#1463192] gluster-block: way to discard passive glfs obj from...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-block
Version: cns-3.9
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Bhumika Goyal
QA Contact: Rahul Hinduja
URL:
Whiteboard:
: 1594112 (view as bug list)
Depends On: 1463192
Blocks: 1594112
TreeView+ depends on / blocked
 
Reported: 2017-06-08 10:53 UTC by Prasanna Kumar Kalever
Modified: 2018-11-19 07:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 07:07:36 UTC
Embargoed:


Attachments (Terms of Use)

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.


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