Salta al contenuto

MSK Broker error when trying to set property fetch.max.bytes

0

Hi,

Why is it not possible to configure the property fetch.max.bytes on MSK Brokers running Kafka version 3.6.0? The following error response is received. It should be definitely possible to configure the property based on Kafka documentation which can be found here.

"errorMessages" : [ "Key 'fetch.max.bytes' is not supported by at least one Apache Kafka version. Key checked against versions: [2.8.1.2, 2.6.2, 2.7.1, 2.8.0, 2.6.3, 2.7.2, 2.8.1, 2.6.0, 2.6.1, 2.7.0, 3.7.x.kraft, 3.3.2, 3.5.1, 3.6.0, 3.7.x, 3.1.1, 3.2.0, 3.3.1, 3.4.0]" ]

posta 2 anni fa564 visualizzazioni

3 Risposte
0

I think that sittings has to be for the consumer. Can you check if this article is helpful: https://learn.conduktor.io/kafka/how-to-send-large-messages-in-apache-kafka/

Can you try for the broker-side setting message.max.bytes instead?

AWS
ESPERTO

con risposta 2 anni fa

  • It's definitely a broker config too - see the link to the Kafka documentation in the question.

0

Hi,

Look at this page to see all MSK parameters you can configure: https://docs.aws.amazon.com/msk/latest/developerguide/msk-configuration-properties.html

Is message.max.bytes a partial solution to your question?

Best,

Didier

ESPERTO

con risposta 2 anni fa

  • Unfortunately not.

0

Here we go,

$ kafka/bin/kafka-configs.sh --bootstrap-server $b --command-config config/client_iam.properties  --entity-type brokers --entity-name 1 --describe --all |grep fetch.max.bytes
fetch.max.bytes=57671680 sensitive=false synonyms={DEFAULT_CONFIG:fetch.max.bytes=57671680}

This IS in fact broker level configuration supported by Kafka broker behind MSK, but MSK Cluster Configuration setup indeed doesn't allow this property to be overridden.

Could you please share your use case for us to to have more information and justification for having fetch request size over 50 MB? Please respond as a comment to this answer.

AWS

con risposta 2 anni fa

  • In short the use case is to increase consumer throughput for data backfill scenarios.

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.