You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the ability to disable azure functions like below to disable the kafka triggers, but we are not sure if this makes sure, that there is no consumer registered at kafka. The reason we are asking is because when we want to reset the offset we get the error "Consumer groups with active members cannot be edited". Does this mean we cannot update the offset when there is "any" consumer connected?
Ideally when the function is disabled the listener for that function should not come up. Since the listener is responsible for creating the connection/consumer, I don't expect the consumer to still be active.
Can you please share where you are running the app - local or which sku are you using for running the app. Depending on where you are running it - restarting the application and observing from the logs if the listener for kafka function is coming up or not should clarify this.
To your question on if you can change the offset with any consumers connected - This is a requirement from Kafka. You would have to ensure to terminate all the consumers - Either by stopping them or waiting for timeouts to occur. Since the consumer from listener will keep on polling after regular intervals - It would have to be explicitly shut down by stopping the app if it is still active.
We are using the ability to disable azure functions like below to disable the kafka triggers, but we are not sure if this makes sure, that there is no consumer registered at kafka. The reason we are asking is because when we want to reset the offset we get the error "Consumer groups with active members cannot be edited". Does this mean we cannot update the offset when there is "any" consumer connected?
{
"name": "AzureWebJobs.SomeKafkaTrigger.Disabled",
"value": false,
"slotSetting": false
},
The text was updated successfully, but these errors were encountered: