Lock issues when clearing cache on Percona XtraDB cluster

Created on 28 May 2020, about 5 years ago
Updated 30 January 2023, over 2 years ago

When using database cache on an Percona XtraDB cluster Truncate's are quite blocking. This means all requests for the cache will wait for the tabel to finish.

When a SST (an initial sync to a new node) is running this can result in waiting for a lock indefinitely which means the sync will fail and the cluster will go down. Other than changing the caching backend to another service, we think not allowing TRUNCATE will aliviate the issues at least. Then we can at least be sure deploying multiple Drupal sites will not result in unfortunate issues where you run into a deadlock situation.

Not too sure what the proper way to fix this would be, but i think removing the possibility for TRUNCATE is at least a start.

🐛 Bug report
Status

Needs work

Version

10.1

Component
Database 

Last updated 3 days ago

  • Maintained by
  • 🇳🇱Netherlands @daffie
Created by

🇳🇱Netherlands bbrala Netherlands

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024