diff --git a/oslo_cache/_memcache_pool.py b/oslo_cache/_memcache_pool.py
index e4411dcb..3193e560 100644
--- a/oslo_cache/_memcache_pool.py
+++ b/oslo_cache/_memcache_pool.py
@@ -215,7 +215,27 @@ class MemcacheClientPool(ConnectionPool):
         self._hosts_deaduntil = [0] * len(urls)
 
     def _create_connection(self):
-        return _MemcacheClient(self.urls, **self._arguments)
+        # NOTE(morgan): Explicitly set flush_on_reconnect for pooled
+        # connections. This should ensure that stale data is never consumed
+        # from a server that pops in/out due to a network partition
+        # or disconnect.
+        #
+        # See the help from python-memcached:
+        #
+        # param flush_on_reconnect: optional flag which prevents a
+        #        scenario that can cause stale data to be read: If there's more
+        #        than one memcached server and the connection to one is
+        #        interrupted, keys that mapped to that server will get
+        #        reassigned to another. If the first server comes back, those
+        #        keys will map to it again. If it still has its data, get()s
+        #        can read stale data that was overwritten on another
+        #        server. This flag is off by default for backwards
+        #        compatibility.
+        #
+        # The normal non-pooled clients connect explicitly on each use and
+        # does not need the explicit flush_on_reconnect
+        return _MemcacheClient(self.urls, flush_on_reconnect=True,
+                               **self._arguments)
 
     def _destroy_connection(self, conn):
         conn.disconnect_all()
diff --git a/releasenotes/notes/bug-1819957-ccff6b0ec9d1cbf2.yaml b/releasenotes/notes/bug-1819957-ccff6b0ec9d1cbf2.yaml
new file mode 100644
index 00000000..c2d54282
--- /dev/null
+++ b/releasenotes/notes/bug-1819957-ccff6b0ec9d1cbf2.yaml
@@ -0,0 +1,24 @@
+---
+fixes:
+  - |
+    [`bug 1819957 <https://bugs.launchpad.net/keystone/+bug/1819957>`_]
+    If a memcache server disappears and then reconnects when multiple memcache
+    servers are used (specific to the python-memcached based backends) it is
+    possible that the server will contain stale data. The default is now to
+    supply the ``flush_on_reconnect`` optional argument to the backend. This
+    means that when the service connects to a memcache server, it will flush
+    all cached data in the server. This change only impacts the pooled backend
+    as it is the most likely (with heavy use of greenlet) to be impacted
+    by the problem and is the recommended production configuration.
+
+    See the help from python-memcached:
+
+    @param flush_on_reconnect: optional flag which prevents a
+            scenario that can cause stale data to be read: If there's more
+            than one memcached server and the connection to one is
+            interrupted, keys that mapped to that server will get
+            reassigned to another. If the first server comes back, those
+            keys will map to it again. If it still has its data, get()s
+            can read stale data that was overwritten on another
+            server. This flag is off by default for backwards
+            compatibility.