How to fix Failed to create consumer binding retrying in 30 seconds AKS

Question

I am runnig microservice applications in Azure AKS.

I can see all of them, reporting an error:

"message":"Failed to create consumer binding retrying in 30 seconds","log.level":"ERROR","logger.name":"org.springframework.cloud.stream.binding.BindingService", "error.class":"org.springframework.cloud.stream.binder.BinderException","error.message":"Exception thrown while starting consumer: "

error.class

org.springframework.cloud.stream.binder.BinderException

error.message

Exception thrown while starting consumer:

error.stack

at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:461) at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:90) at org.springframework.cloud.stream.binder.AbstractBinder.bindConsumer(AbstractBinder.java:143) at org.springframework.cloud.stream.binding.BindingService.lambda$rescheduleConsumerBinding$1(BindingService.java:201) at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

Could you please advise?

Answer 1

Hi Chalamova,

Have this ever worked before or is it something you are implementing first time? It looks like a misconfiguration to me on Binder config at spring.cloud.stream.bindings.

• Please, try manually connecting to the broker from within an AKS pod using: nc -zv <BROKER_HOST> <BROKER_PORT>
• If your AKS cluster is configured with private networking, ensure that the broker’s DNS is resolvable. kubectl exec -it <pod-name> -- nslookup <BROKER_HOST>
• Also good to check if the actual Broker Topic exits in Kafka or not. If it does then may be restart the binding and try to manually rescheduling if it helps

Hope this helps, please let me know if any questions.

Thanks,

Abdul