9/27/2023 0 Comments Lock queue lock 52After lengthy tracing it was determined that certain Craft::$app->getCache() and setCache() calls in a module (custom FeedMe feed type) were falling back to the FileMutex, because this cached data exceeded the max 1 MB limit of a single memcache key, so therefore it would not be cached in memcache on staging/live but instead use the FileMutex. We found on staging and live constant mutex locking errors with the queue but not on dev no matter how much we tried to reproduce it. The mutex component had not been modified in the app.php since the 3.7.20 change. We had a Craft CMS site using memcache on our staging and live environments, but locally on dev, using Redis which is a bit of mix, but just because Nitro provides the capability effortlessly. Just in case someone else comes across this, I want to provide a potential caveat/edge case of the file mutex now being default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |