You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some benchmarking and load testing has been done as part of #436, showing that an exception is thrown when multiple parallel users try to create new short URLs which include both existing and new tags.
Some of them work, but others fail because they try to insert the existing tags as if they were new, throwing an error due to a duplicated key:
The issue only happens when serving the app with swoole, and only if more than one worker is used.
It feels like all workers are sharing either the EntityManager, the unit of work or the database connection, but swoole docs say every worker has it's own instance of the app and they don't share the memory.
How Shlink is set-up
Summary
Some benchmarking and load testing has been done as part of #436, showing that an exception is thrown when multiple parallel users try to create new short URLs which include both existing and new tags.
Some of them work, but others fail because they try to insert the existing tags as if they were new, throwing an error due to a duplicated key:
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'foo' for key 'UNIQ_6FBC94265E237E06'
The issue only happens when serving the app with swoole, and only if more than one worker is used.
It feels like all workers are sharing either the EntityManager, the unit of work or the database connection, but swoole docs say every worker has it's own instance of the app and they don't share the memory.
https://github.com/swooletw/laravel-swoole/wiki/2.-Swoole-Structure
The text was updated successfully, but these errors were encountered: