How can you avoid the base lock error when using cluster and sequelize?

Question

MySQL

When using cluster and sequelize gives table lock errors. Which, in principle, is logical since one worker is already recording. Tell me how to make sequelize understand that the request has already left and there is no need to send it again from other workers.

Answer 1

It seems to me that you have problems in terms of architecture. Not comme il faut if different workers do the same operation on the same cell. If these are competitive requests from different users, then it is quite normal that if someone edits, then others are waiting.