Hi Phil, Config ConsumerConfig.METADATA_MAX_AGE_CONFIG has default 300000 ms. This config drives a mechanism where a proactive meta data refresh request is issued by consumer periodically. i have seen that i get log about successful heartbeat along with commit only before this request. once this request is issued then next successful heartbeat is only after next poll. This will cause a rebalance and mark current consumer dead if there is no poll in next 30 seconds after meta refresh (where session time is 30 seconds.)
Regards, Vinay
