jmap-set-lock

[michalcharvat]

Do you have any suggestions on how to avoid jmap-set-lock errors? I have one idea, but it would mean storing the data outside of GO. Currently, data is coming to the server every 3-4 seconds, plus some additional user activities. Logging on the model is disabled, and I also tried setting $trackChanges = false, but that didn’t help. I have to restart the web server and clear caches every 24 hours to resolve the error. I think some communication between the client and server should be replaced with WebSockets, as these frequent changes can easily overload the server.

[michalcharvat]

When I see the comment // on deadlocks retry 10 times, I assume you're aware of some limit, aren't you? Another problem in future could be with core_change table - ID is just signed integer - in my case 70 000 000+ of 2 147 483 647 instead of unsigned or even better bigint. As I understand you just delete records from that table instead of truncate.

I think there's a bug because you can't disable $trackChanges on a specific model due to self...

so only what you can is disable \go\core\jmap\Entity::$trackChanges = false; before each update... which will have probably some consequences.