-
Notifications
You must be signed in to change notification settings - Fork 44
Deserialization error #46
Comments
Hello, |
This is probably because of the following optimization:
This was fixed internally. We need to make a new release. |
@verdie-g when can I expect the new release ? I hope it will be soon. Please fill me on that. |
I just need to merge #47 |
The partial message thing was already taken care of when deserialising message sets. The new problem was introduced when supporting record batches? |
Precisely. Should be ok with the fix. |
hi, when i subscribe to topic, k# throws exception like below
here my configs producer
consumer
|
Error : A response could not be decoded for the node - Kafka.Protocol.ProtocolException: The record batch says it has length that stops at 1049715 but the list of all batches stop at 1048641.
Throws : Could not deserialize a message for topic xyz / partition 2. Because our configuration is set to 'ConsumerErrorStrategy == Discard', we will now read from latest offset.
In my consumer, I am seeing the above error intermittently and whenever I receive this error, it discards a whole lot of messages from that partition.
So for example I receive this error in partition -2 offset (5100), whenever it resumes to consume from that partition it starts from the latest for example offset (9000). It discards the 4000 messages and I lose them.
Can you help me by explaining what may be wrong or what your library does in this case, and any ideas how to overcome such scenario.
The text was updated successfully, but these errors were encountered: