Red Hat Bugzilla – Bug 1459850
gluster-block: way to discard passive glfs obj from cache
Last modified: 2017-06-28 07:27:10 EDT
Description of 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.
Because, current lru cache Hashing is based on volume name.
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