Redis-based distributed lock repeat notification solving method

Abstract

The invention provides a Redis-based distributed lock repeat notification solving method. The method comprises the following steps: S1, adopting a Redis set as a filter; s2, storing the message ID, judging whether the ID value of the message ID is an integer or not by Redis internal storage, and storing the message ID in a Redis set; s3, checking whether the messages are repeated or not; s4, informing a message queue. A Redis set is adopted as a filter, a message ID is stored in the Redis set, whether the message is repeated or not is judged by checking whether the message ID exists in the Redis set or not, a message queue is informed that the message is processed for the repeated message, the message does not need to be informed again, the effect that the message queue cannot repeatedly inform the same message is achieved, and therefore, the problem of repeated consumption of messages is solved.

Description

technical field [0001] The present invention relates to the field of data processing, and specifically, the present invention relates to a method for solving repeated notification based on Redis distributed locks. Background technique [0002] There will be requirements for asynchronous data processing or data batch processing between application systems, such as asynchronous notification of transaction results, asynchronous processing of large data file generation, data communication between operating systems and customer systems, etc. One of the solutions is The message queue is used as the transmission medium to realize asynchronous data transmission. [0003] Normally, after the message queue receives the message, it will push it to the message consumer as low as possible in a timely manner. The consumer fetches the data from the message queue. After receiving the confirmation response from the message consumer within the specified response time , the message queue will...

AI Technical Summary

Problems solved by technology

[0004] However, in the existing technology, in many scenarios, the message processing logic of the consumer is often more complicated. In many cases, the consumer may need to perform CRUD database operations, or may call remote interfaces such as the operator’s SMS interface, or the consumer’s Machine performance issues of physical machines, etc., to fulfill business requirements

In this case, the consumer's confirmation response cannot respond to the message queue within the specified response time, and the message queue will think that the other party has not received the message and push it to the consumer again. At this time, the problem of repeated message consumption will occur

For example, asynchronous notification of transaction results: when a 1 yuan transaction occurs in system A, system A notifies system B of the transaction result through the message queue, and system B is responsible for notifying users and merchants. System B is the consumer. If the processing is slow and exceeds Responding to the message queue without specifying the response time, there will be a problem of repeated message consumption. At this time, the user and the merchant will receive two 1 yuan transaction results, which will cause unnecessary misunderstandings and disputes

Images