oslo.cache Release Notes - en to en_GB translation catalogue (6 entries)

en: Add new options (``hashclient_retry_attempts``, ``hashclient_retry_delay``, ``dead_timeout``) to allow to configure pymemcache's HashClient use through dogpile.cache's pymemcache backend. Those options expose pymemcache params that allow to configure the failover for memcached cluster.
en_GB: Add new options (``hashclient_retry_attempts``, ``hashclient_retry_delay``, ``dead_timeout``) to allow to configure pymemcache's HashClient use through dogpile.cache's pymemcache backend. Those options expose pymemcache params that allow configuring the failover for memcached cluster.

en: But unfortunatelly this option is causing another issue. If memcache server disappears, or client had broken connection to memcache server, clients start to flush server on reconnect.
en_GB: But unfortunately, this option is causing another issue. If memcache server disappears, or the client had a broken connection to memcache server, the clients start to flush the server on reconnect.

en: Simply said this option can cause loop of flushs and overloaded memcached servers. This change is moving optional parameter `flush_on_reconnect` to oslo.cache config.
en_GB: Simply said this option can cause loop of flushs and overloaded memcached servers. This change is moving the optional parameter `flush_on_reconnect` to oslo.cache config.

en: This means that network connections will go UP and can cause server to be overloaded until memcache will be unresponsive.
en_GB: This means that network connections will go UP and can cause the server to be overloaded until memcache will become unresponsive.

en: [`bug 1743036 <https://bugs.launchpad.net/oslo.cache+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 behavior of the ListOpt used by `memcache_servers` option.
en_GB: [`bug 1743036 <https://bugs.launchpad.net/oslo.cache+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.

en: [`bug 1888394 <https://bugs.launchpad.net/oslo.cache/+bug/1888394>`_] 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. To avoid this, param flush_on_reconnect was used in code.
en_GB: [`bug 1888394 <https://bugs.launchpad.net/oslo.cache/+bug/1888394>`_] 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. To avoid this, param flush_on_reconnect was used in the code.
