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
Describe the bug
I have set the value of maxBytesPerPartition to 1 and when i produce a message as big as 126KB, the message still get consumed, wherein the documentation it is stated that
The maximum amount of data per-partition the server will return. This size must be at least as large as the maximum message size the server allows or else it is possible for the producer to send messages larger than the consumer can fetch. If that happens, the consumer can get stuck trying to fetch a large message on a certain partition
which means the consumer should be stuck and the message should not be consumed.
To Reproduce
you can try setting this value to 1 and produce a very big message.
Expected behavior
the consumer should be stuck and no message should be consumed.
Observed behavior
the message still get consumed.
Environment:
OS: Mac OS 14.2.1
KafkaJS: version 1.13.0
Kafka version: 3.1.0
NodeJS version: 14.18.0
The text was updated successfully, but these errors were encountered:
Describe the bug
I have set the value of maxBytesPerPartition to 1 and when i produce a message as big as 126KB, the message still get consumed, wherein the documentation it is stated that
The maximum amount of data per-partition the server will return. This size must be at least as large as the maximum message size the server allows or else it is possible for the producer to send messages larger than the consumer can fetch. If that happens, the consumer can get stuck trying to fetch a large message on a certain partition
which means the consumer should be stuck and the message should not be consumed.
To Reproduce
you can try setting this value to 1 and produce a very big message.
Expected behavior
the consumer should be stuck and no message should be consumed.
Observed behavior
the message still get consumed.
Environment:
The text was updated successfully, but these errors were encountered: