Skip to content

C
configuration
Commit bc4ae5bc by Clinton Blackburn
Options

Updated discovery service to use pylibmc instead of python-memcached 

python-memcached seems to have sporadic issues with Python 3.5.

ECOM-4370
parent f8ae68f8
Showing with 2 additions and 1 deletions
playbooks/roles/discovery/defaults/main.yml
...@@ -47,7 +47,7 @@ DISCOVERY_MEMCACHE: [ 'memcache' ] ...@@ -47,7 +47,7 @@ DISCOVERY_MEMCACHE: [ 'memcache' ]
DISCOVERY_CACHES: DISCOVERY_CACHES:
default: default:
BACKEND: 'django.core.cache.backends.memcached.MemcachedCache' BACKEND: 'django.core.cache.backends.memcached.PyLibMCCache'
KEY_PREFIX: '{{ discovery_service_name }}' KEY_PREFIX: '{{ discovery_service_name }}'
LOCATION: '{{ DISCOVERY_MEMCACHE }}' LOCATION: '{{ DISCOVERY_MEMCACHE }}'
...@@ -178,5 +178,6 @@ discovery_debian_pkgs: ...@@ -178,5 +178,6 @@ discovery_debian_pkgs:
- libmysqlclient-dev - libmysqlclient-dev
- libssl-dev - libssl-dev
- libffi-dev # Needed to install the Python cryptography library for asymmetric JWT signing - libffi-dev # Needed to install the Python cryptography library for asymmetric JWT signing
- libmemcached-dev # Needed for pylibmc
discovery_redhat_pkgs: [] discovery_redhat_pkgs: []
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment