ksdvishnukumar

Hi @rtfleg, As per my understanding from other threads, Consumer B does not get assigned the partitions until PartitionsRevokedHandler get completed. In this delegate only you are planning to commit...

Yes the property and description dies not match. But workaround for this is use the SetConfig method to pass the internal configuration property name and set the comma seperated value...

@Pablovide I see that erroendue to Serializer.. For the Custom model you need to register the SetSerializer method with the Custom Serializer class derived from ISerializer interface. That should work...

Hi @anchitj , I also faced the same issue. In my case, broker is reachable only. @rashmiann Did you able to resolve this error?

@roshanmt I see you are using the CancellationToken in the consume method. I am assuming there might be a code where it's cancelling the Token in the different thread in...

Couple of observation now after tuning the below configuration. MaxPartitionFetchBytes to 1048576 (Default Value) FetchMaxBytes to 102400 message.max.bytes to 102399 CancellationDelayInMs to 10 With this I can see the Throttling...

Updating the question in this Comment **Problem Statement** Single consumer is consuming the message from the single topic partition. The consuming topic partition has 8578 messages The observation from Azure...

@mhowlett, @edenhill and Confluent Inc Members Any update on this?

Hi @mhowlett , @edenhill Is there any workaround on this can be implemented based on the Consumer configuration?