yahoo-eng-team team mailing list archive

[Dina Belova <dbelova@xxxxxxxxxxxx>]

Public bug reported:

== Abstract ==

I'm profiling Keystone using OSprofiler tool and the appropriate
Keystone+OSprofiler integration changes -
https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic
:osprofiler-support-in-keystone - currently on review. The idea was to
analyse how does Keystone use DB/Cache layers.

== Expected ==

The local context cache added during Mitaka should cache key-value pairs
per every keystone request and grab cached value from it where possible
in memoize instead of hitting to Memcache.

== Observed ==

During the nova-boot request keystone API is hit 3 times including all
python clients work. If we'll take a look, for instance, on the
get_domain function, it's called twice per one API call, and both times
it's going to the Memcache without local cache usage.

Memcache points can appear in the trace only if memcache is *really*
used, not just try to grab value from it. Also
/opt/stack/keystone/keystone/common/cache/_context_cache.py file was
modified to check if
https://github.com/openstack/keystone/blob/master/keystone/common/cache/_context_cache.py#L78-L80
were called == local cache used. Nothing?

** Affects: keystone
     Importance: Undecided
         Status: New

** Attachment added: "server_create.html"
   https://bugs.launchpad.net/bugs/1567403/+attachment/4627480/+files/server_create.html

-- 
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/1567403

Title:
  Local context cache seems to work unproperly

Status in OpenStack Identity (keystone):
  New

Bug description:
  == Abstract ==

  I'm profiling Keystone using OSprofiler tool and the appropriate
  Keystone+OSprofiler integration changes -
  https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic
  :osprofiler-support-in-keystone - currently on review. The idea was to
  analyse how does Keystone use DB/Cache layers.

  == Expected ==

  The local context cache added during Mitaka should cache key-value
  pairs per every keystone request and grab cached value from it where
  possible in memoize instead of hitting to Memcache.

  == Observed ==

  During the nova-boot request keystone API is hit 3 times including all
  python clients work. If we'll take a look, for instance, on the
  get_domain function, it's called twice per one API call, and both
  times it's going to the Memcache without local cache usage.

  Memcache points can appear in the trace only if memcache is *really*
  used, not just try to grab value from it. Also
  /opt/stack/keystone/keystone/common/cache/_context_cache.py file was
  modified to check if
  https://github.com/openstack/keystone/blob/master/keystone/common/cache/_context_cache.py#L78-L80
  were called == local cache used. Nothing?

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