Contrib.social

Lock issues when clearing cache on Percona XtraDB cluster

Open on Drupal.org →
Created on 28 May 2020, over 4 years ago
Updated 17 February 2023, almost 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 2 days ago

  • Maintained by
  • 🇳🇱Netherlands @daffie
Created by

🇳🇱Netherlands bbrala Netherlands

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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.

  • Comment almost 2 years ago →
    🇺🇸United States smustgrave

    CI failures for #11

  • Status changed to Needs review almost 2 years ago
  • Comment almost 2 years ago →
    🇮🇳India ankithashetty Karnataka, India

    Not sure if this is the fix to CI errors, but think it'll work...

  • Status changed to Needs work almost 2 years ago
  • Comment almost 2 years ago →
    🇺🇸United States smustgrave

    This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

    This could use an issue summary update using the default issue template. What's the proposed solution? What's the remaining tasks? Example this will need a test case to show the issue

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024