🇬🇧United Kingdom @rich.3po

Following up on the case referenced in #54 and #51 (which is the same application).

We believe comment #51 can be disregarded, as we only observed this at one stage, and we believe this was down to a deployment or cache flushing issue of some kind.

So in summary, the patch in #45 seems to be working well, so long as cache bins which have a default_backend set are explicitly overridden in settings.php.

See https://www.drupal.org/node/2754947 → .

e.g for the discovery bin:

$settings['cache']['bins']['discovery'] = 'cache.backend.memcache_transaction_aware';

Can the module maintainers please comment on the overall approach used here, and advise if this patch is likely to make it back into the main project?