Bug 1302811 - backport the metadata_cache_expiration config option to avoid harcoded value of 15s
Summary: backport the metadata_cache_expiration config option to avoid harcoded value ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 5.0 (RHEL 6)
Assignee: Sven Anderson
QA Contact: nlevinki
URL:
Whiteboard:
Depends On: 1302401 1302812 1302813
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 16:51 UTC by Sven Anderson
Modified: 2019-09-09 16:00 UTC (History)
12 users (show)

Fixed In Version: openstack-nova-2014.1.5-22.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of: 1302401
Environment:
Last Closed: 2016-03-21 18:35:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1366139 0 None None None 2016-01-28 16:51:36 UTC
OpenStack gerrit 159264 0 None None None 2016-01-28 16:51:36 UTC

Description Sven Anderson 2016-01-28 16:51:37 UTC
+++ This bug was initially created as a clone of Bug #1302401 +++

The metadata cache expiration timeout was hardcoded to 15 seconds in versions older than kilo (OSP7).

In kilo a new configuration option was added:

  'metadata_cache_expiration',

  Time in seconds to cache metadata; 0 to disable
  metadata caching entirely (not recommended). Increasing
  this should improve response times of the metadata API
  when under heavy load. Higher values may increase memory
  usage and result in longer times for host metadata
  changes to take effect.

introduced in:

  https://review.openstack.org/159264

This config option should be backported to OSP5 in order to provide the same flexibility and avoid premature cache expiration in cases where the metadata is highly static.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-01-27 13:30:20 EST ---

Since this issue was entered in bugzilla without a release flag set, rhos-8.0? has been automatically added to ensure that it is properly evaluated for this release.

Comment 2 Lon Hohberger 2016-03-15 20:11:56 UTC
According to our records, this should be resolved by openstack-nova-2014.1.5-29.el6ost.  This build is available now.


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