Set [keystone_authtoken] memcache_use_advanced_pool to avoid bursting connections to memcached
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Takashi Kajinami |
Bug Description
Description
===========
This issue was initially reported in the following downstream bug.
https:/
We noticed sometimes memcached has huge number of connections established and hit max connection limit(8192 by default).
Looking at all connections, it turned out specific services like neutron have huge number (thousands) of connections with memcached, which is triggered by keystonemiddleware.
While we'd need to identify the root cause in keystonemiddleware, so far setting the following parameter works as a valid workaround and we no longer observe bursting connections with this setting.
~~~
[keystone_
memcache_
~~~
This bug is to track an effort to add a tht parameter to set that keystone_authtoken parameter.
Steps to reproduce
==================
1. Deploy overcloud
2. Execute API requests periodically
3. Monitor number of connections established with memcached
Expected result
===============
Number of connections stays at some point
Actual result
=============
Number of connections keeps growing
Environment
===========
The issue was initially found in stable/train
Logs & Configs
==============
N/A
description: | updated |
Changed in tripleo: | |
assignee: | nobody → Takashi Kajinami (kajinamit) |
importance: | Undecided → High |
Fix proposed to branch: master /review. opendev. org/c/openstack /tripleo- heat-templates/ +/795010
Review: https:/