yahoo-eng-team team mailing list archive

[OpenStack Infra <1590779@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/349704
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=42eda48c78f1153081b4c193dc13c88561409fd3
Submitter: Jenkins
Branch:    master

commit 42eda48c78f1153081b4c193dc13c88561409fd3
Author: David Stanek <dstanek@xxxxxxxxxxx>
Date:   Mon Aug 1 21:06:50 2016 +0000

    Distributed cache namespace to invalidate regions
    
    dogpile.cache's region invalidation is not designed to work across
    processes. This patch enables distributed invalidation of keys in a
    region.
    
    Instead of using a static cache key, we use the original cache key
    and append a dynamic value to it. This value is looked up in
    memcached using the region name as a key. So anytime the value of
    the region key changes the cache keys in that region are
    effectively invalidated.
    
    Closes-Bug: #1590779
    Change-Id: Ib80d41d43ef815b37282d72ad68e7aa8e1ff354e


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1590779

Title:
  Cache region invalidation works for local CacheRegion object only

Status in OpenStack Identity (keystone):
  Fix Released
Status in oslo.cache:
  In Progress

Bug description:
  oslo_cache uses dogpile.cache's CacheRegion
  which invalidates by setting region object attributes:
  - self._hard_invalidated
  - self._soft_invalidated
  Then it checks these attributes on value get.
  So this invalidation works for particular region object only.

  If there is a need to invalidate a region so that values in it are no
  more valid for other instances of CacheRegion (either in the same
  process or in another one) - it's simply impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1590779/+subscriptions