The case has been solved --- no matter how to change the code from the logic of MQ consumption, it will not take effect

A from MQ How to change the code of consumption logic will not take effect , Back and forth several times , I don't understand

Add a log to the consumption logic , Discovery tm No printing , How to change the logic doesn't seem to reflect , However, other business changes are effective , Only from the MQ The logic of consumption does not work .

Finally, let's see MQ The number of consumers found a problem , My test environment has only two machines ,MQ Consumers only have 40 individual , But I am MQ I saw it on the management platform 120 Consumers , O & M secretly added machines to me ？ That's impossible , Put strangers ip Let the operation and maintenance see if k8s Some containers were omitted during rolling release and were not supervised , It turned out to be ....

This problem is very difficult to find , Because all traffic operation and maintenance have been switched , The logging system has also been switched , Including your monitoring system, your normal non consumer business will go through the new server, and the natural changes will take effect , But all services will no longer take over your previous Services , Only the consumption queue logic will fall into this old service ... It's really hard to find this problem without looking at the number of consumers .