- Issue created by @janusman
- First commit to issue fork.
- Status changed to Fixed
3 months ago 3:24am 27 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.
Under some cases, like a temporarily missing Memcache instance behind mcrouter, the module may start logging failures.
While logging is good, it can also be bad (when it's too much) and can clog up the Database or syslog logs.
The previous release's behavior was different; it seems there was a change in this line in the MemcachedDriver.php class:
8.x-2.5:
if (!$result && $this->settings->get('debug')) {
8.x-2.6: (wrong?)
if (!$result || $this->settings->get('debug')) {
There is no mention of this behavior change in the README so I'm flagging this as a bug.
Don't have a set of steps, but I think we could create one by configuring a local Drupal so that only a single cache bin points to memcache, then stop the local memcache service, and run some drush snippet that tries to reach that. Or, this may need mcrouter as a middleman and then stop the backend memcache instance...?
Change || back to && above.
Create Merge request.
None
None
None
Fixed
2.6
Code
Automatically closed - issue fixed for 2 weeks with no activity.