Today, the three parties met two people with me feedback, asynchronous interface features a micro service is not normal, because the program uses asynchronous interface Kafka asynchronous message, the caller said Kafka did not receive notice to consumers, according to this problem, contact the relevant personnel were analyzed:
If (a) clear environmental agreement
1, link producers and consumers Kafka's address is the same, preliminary findings A square consumers link Kafka address is incorrect, there is no consistent link with the address of the producer of Kafka.
2, topic and key if all agree, initially to determine the topic and the consumer side A key topic with both producers and key is one to one.
The interaction between the (two) producers and Kafka
By analyzing the log producers, it has successfully occurred to Kafka the message, and at the end made it clear that Kafka received the second message, so that interaction between producers and Kafka is not a problem, the process is normal.
The interaction between the (three) Kafka and consumers
1, A square test after consumer Kafka link address correction, indicating that can be received properly, this issue A square consumers have been addressed, that is not caused by incorrect address;
2, B No consumer side receiving the notification, Kafka confirmed party, party B at consumers do not subscribe topic of producers, consumers, and party B does not start when seen in the topic log information, Kafka side B side to let consumers amend topic information and key information, write to die in the code; B test after modifications consumer side, indicating a normal message is received, and also seen in Kafka there there are B side of consumers subscribed to this topic, this B-side to the consumer's problem handling, and key topic is not caused by incorrect.
Summary: In the face of such problems be sure to check their own code, configuration information is normal, otherwise such an analysis and positioning is a waste of everyone's time.