- Issue created by @ragnarkurm
- π©πͺGermany marcoliver Neuss, NRW, Germany
Hi ragnarkurm, if you have the time, could you please fill in the Steps to reproduce section? I pumped a database full with access-restricted nodes but I was not able to produce a significant slowdown.
- Status changed to Postponed: needs info
over 1 year ago 11:00am 12 October 2023 - π©πͺGermany marcoliver Neuss, NRW, Germany
Marking as postponed until there are actionable Steps to Reproduce.
- πΊπΈUnited States crutch
We are getting some page timeouts with similar logs. It seems to only happen when it is yet to be cached. Upon refresh of the url, after the "unexpected error..." message on a white page, it will load. I've not tried the patch yet.
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY000]: General error: 3024 Query execution was interrupted, maximum statement execution time exceeded: SELECT DISTINCT "t"."nid" AS "nid" FROM "taxonomy_index" "t" WHERE "t"."nid" NOT IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2, :db_condition_placeholder_3, :db_condition_placeholder_4, :db_condition_placeholder_5, :db_condition_placeholder_6, :db_condition_placeholder_7, :db_condition_placeholder_8, :db_condition_placeholder_9, :db_condition_placeholder_10, :db_condition_placeholder_11, :db_condition_placeholder_12, :db_condition_placeholder_13, :db_condition_placeholder_14, :db_condition_placeholder_15, :db_condition_placeholder_16, :db_condition_placeholder_17, :db_condition_placeholder_18, :db_condition_placeholder_19, :db_condition_placeholder_20, :db_condition_placeholder_21, :db_condition_placeholder_22, :db_condition_placeholder_23, :db_condition_placeholder_24, :db_condition_placeholder_25, :db_condition_placeholder_26); Array ( [:db_condition_placeholder_0] => 7569 [:db_condition_placeholder_1] => 7570 [:db_condition_placeholder_2] => 7571 [:db_condition_placeholder_3] => 7572 [:db_condition_placeholder_4] => 7573 [:db_condition_placeholder_5] => 7574 [:db_condition_placeholder_6] => 7575 [:db_condition_placeholder_7] => 7576 [:db_condition_placeholder_8] => 7626 [:db_condition_placeholder_9] => 7976 [:db_condition_placeholder_10] => 7977 [:db_condition_placeholder_11] => 8453 [:db_condition_placeholder_12] => 8806 [:db_condition_placeholder_13] => 1645 [:db_condition_placeholder_14] => 1646 [:db_condition_placeholder_15] => 1647 [:db_condition_placeholder_16] => 1648 [:db_condition_placeholder_17] => 1649 [:db_condition_placeholder_18] => 1650 [:db_condition_placeholder_19] => 1651 [:db_condition_placeholder_20] => 1652 [:db_condition_placeholder_21] => 7577 [:db_condition_placeholder_22] => 7882 [:db_condition_placeholder_23] => 7890 [:db_condition_placeholder_24] => 8475 [:db_condition_placeholder_25] => 9211 [:db_condition_placeholder_26] => 7588 ) in Drupal\permissions_by_term\Service\AccessStorage->getUnrestrictedNids() (line 732 of /drupal/web/modules/contrib/permissions_by_term/src/Service/AccessStorage.php).
- πΊπΈUnited States crutch
We continue to get PHP errors. Sometimes it reports the AccessStorage.php and sometimes CachePluginBase.php. It's obvious that pages are slow to load with some timing out. This error comes from a page/content type that doesn't contain a PBT field. I've added a document with some more detail about the most recent error.
- π©πͺGermany Peter Majmesku π©πͺDΓΌsseldorf
Hi crutch, it looks like your database server reached limits. Yes, PbT needs some resources on the database site. Even we do have already optimized here really a lot. From your report I do not see, how PbT could be optimized more, to help you out.
It might be a good approach to check the database server resources and configs there.
max_statement_time setting in your my.cnf could be a place to optimize your database server settings. E.g.:
[mysqld]
max_statement_time = 300 # 5 minutesHowever, database server optimization is not in the scope of the PbT module. That is a different topic.
- πΊπΈUnited States crutch
Thank you for the quick response :) Affirmative, understand that it would not be PbT. Database max_execution_time is set to 300 currently.