Problem/Motivation

Using the current Memcache report can not report statistics on any other cluster than default.

Steps to reproduce

Visit the current statistics page in a multiple clustered site and add the '/' cluster name to the URL and it displays default.

Proposed resolution

Display links to the other clusters.

Remaining tasks

None

User interface changes

It now displays links to all the configured clusters with configured cache bin names and these are links to to statistics pages displaying information from that cluster.

API changes

None

Data model changes

None

CommentFileSizeAuthor
#2 memcache-improve_statistic_page_for_multiple_servers-2.patch5.64 KBsomersoft
memcache-improve_statistic_page_for_multiple_servers.patch3.31 KBsomersoft

Issue fork memcache-3373237

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

somersoft created an issue. See original summary.

somersoft’s picture

somersoft commented
StatusFileSize
new memcache-improve_statistic_page_for_multiple_servers-2.patch5.64 KB

Updated the patch so that

  1. The controller now uses the 'memcache.settings' service to obtain configuration information.
  2. the class \Drupal\memcache\Driver\DriverBase also uses the 'memcache.settings' service to obtain configuration information after checking the information from the configFactory.

japerry made their first commit to this issue’s fork.

japerry’s picture

japerry
Location KOMK
commented

While investigating this further, I noticed we are using config instead of settings.php for the driver settings. That seems wrong. I've made a change record and will note it in the 2.6 release notes. https://www.drupal.org/node/3460878

japerry opened merge request !31

  • japerry committed 942de081 on 8.x-2.x 
    Issue #3373237: Improve statistic page for multiple servers
japerry’s picture

japerry
Location KOMK
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.