Search before asking
Description
Both Kafka and Pulsar enforce limits on the server side:
[1] In Pulsar, the maxMessageSize parameter can be configured on the server, with a default value of 5 MB (see: https://pulsar.apache.org/docs/next/concepts-messaging/).
[2] In Kafka, the socket.request.max.bytes configuration (often associated with socket.send.buffer.bytes) has a default value of 100 MB (see: https://kafka.apache.org/42/configuration/broker-configs/#brokerconfigs_socket.request.max.bytes).
Similarly, Fluss should introduce a configurable parameter named netty.server.max-request-size, with a default value of 100 MB.
（In our production environment, we have write batch.size values reaching several tens of megabytes; therefore, we require this limit to be set higher.）
Willingness to contribute
Search before asking
Description
Both Kafka and Pulsar enforce limits on the server side:
[1] In Pulsar, the maxMessageSize parameter can be configured on the server, with a default value of 5 MB (see: https://pulsar.apache.org/docs/next/concepts-messaging/).
[2] In Kafka, the socket.request.max.bytes configuration (often associated with socket.send.buffer.bytes) has a default value of 100 MB (see: https://kafka.apache.org/42/configuration/broker-configs/#brokerconfigs_socket.request.max.bytes).
Similarly, Fluss should introduce a configurable parameter named netty.server.max-request-size, with a default value of 100 MB.
（In our production environment, we have write batch.size values reaching several tens of megabytes; therefore, we require this limit to be set higher.）
Willingness to contribute