New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Percona XtraDB Cluster prohibits use of GET_LOCK #14919
Comments
Can you try the latest beta? This particular get_lock might be removed. |
Sure :)
|
Do you have a DB reader configured? Do you use any plugins besides any plugins from Matomo/InnoCraft? Are they all up to date? |
I use only plugins included with Matomo, I didn't installed any external ones yet, in settings I see
I run multiple Matomo Docker containers on k8s |
Percona XtraDB Cluster allows you to create temporary tables right? I suppose it would have triggered a different error if not. |
something like |
Yep, it's ok, no error. IIRC creation of tmp table and operating on it should be inside one transaction, right? Outside transaction it will disappear. Maybe it's the case here? I had really long break for writing SQL and real code recently so not sure :) |
The table should exist until the DB connection is interrupt / closed (the session is closed) or until we delete the table. I'm not sure if XtraDB Cluster would behave differently here for some reason. We haven't had any issues with this so far otherwise. |
Patch with archiving without LOCK works correctly :) It's possible that ProxySQL is not handling correctly SQL queries with temp tables that Matomo is currently using. Related: sysown/proxysql#939 |
Hi,
I moved my Matomo instance recently from standard MariaDB master/slave setup to PXC multi master.
Running web interface seems fine but archiving in cron task doesn't work, this is a part of error:
Is there any workaround or chance to skip table locks for cron?
AFAIK changing
pxc_strict_mode
to something other thanENFORCING
is a bad idea and that can break data in DB.Maybe some optional flag for
core:archive
task like--skip-locks
with some word of warning ?I'm not sure if in Matomo code there is a ability to totally skip lock and data can be still OK.
This comment kinda suggests that Matomo should work without locks but it's not working for me:
matomo/core/Db.php
Line 509 in 54fa685
EDIT:
I found this pull request merged to future v3.12.0, can this change solve this error?
#14788
The text was updated successfully, but these errors were encountered: