Data duplication problem caused by Dubbo timeout retry mechanism

Data duplication problem caused by Dubbo timeout retry mechanism

http://blog.csdn.net/angry_tiger/article/details/51073459

 

 

When submitting data, go to redis to find the token_id key. If it is not found, if it is empty, put (token_id, token value)
until the submission is completed, clear the value of the token and remove it, remove (token_id, null)
if it has not been submitted , the value of the token will exist. When the second and third N resubmissions are made, as long as the token still has a value, it will not be executed anymore. Get it, send me a red envelope.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326390802&siteId=291194637