the dubbo service of the project is deployed on 4 servers. There is a problem that I call the dubbo interface in controller, and the interface will insert some data, but I found in the background that 2 dubbo servers executed this interface in the same second, resulting in repeated insertion of a piece of data. why did this happen?
even if you have only one machine, the retry mechanism of dubbo may lead to repetition, so you have to design your interface as idempotent
. The retry of any link will not affect
by adding trace to check, or look at the requested link. Why
is the cause of load balancing strategy? Take a look at the loadbalance settings of your consumer
I have this problem because the entity that returned the value is not serialized, and the entity serialization problem is resolved.
Previous: What does the 80001 prompt mean in vscode?
Next: Problems encountered in springboot global exception handling
ReferenceConfig(null) is not DESTROYED when FINALIZE, dubbo version: 2.5.3, current host: 10.16.4.157 ...
dubbo degrades the service, and the mock, timed out or the number of retries reached the upper limit will go to mock . How to recover? There are some articles on the Internet about asynchronous thread detection, how to do it? ...