Hello, I have been running consumer with connectionTTL=10000 for some time. Recently I noticed that when the consumer takes longer than 10 sec to process the message I got connection error. This makes sense to me because the server will clear the session after 10 sec (maybe 2 second more due to ttl-check-interval) and thus making the consumer fail to use the same session to ack. Since I am running a cluster of 2 brokers, I think I have to use connectionTTL to make message redistribution work since the server need to clear the consumer connection to be ready for redistribution when the consumer restarts and connects to the other broker. Thus, connectionTTL has to be shorter than the time kubernetes restart the consumer (about 15 sec), however this has to be more than the max time a consumer needs to process a message (around 2 mins). I now think my use of connectionTTL as a way to notify the broker that the consumer has disconnected is not right. Is there another config that I need to use?
Regards Thai Le
