Stein Series Release Notes¶
[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_reconnectoptional 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.
[bug 1743036] The backend_argument value(s) for url when configuring memcache did not properly handle multiple servers. This is because the URL was passed as a string (comma delimited) instead of a list to the memcache library/client. The url argument is now special cased and will split the string on a comma so that it mirrors the behaviour of the ListOpt used by memcache_servers option.