kubernetes - Kubernetes中的max.request.size Kafka

标签 kubernetes apache-kafka

我正在尝试在kubernetes中将max.request.size赋予Kafka,似乎不起作用。怎么做?

我也尝试过使用KAFKA_MAX_REQUEST_SIZE再次没有任何正面结果:

  spec:
  containers:
  - name: kafka
    image: wurstmeister/kafka
    ...

    env:
    - name: KAFKA_ZOOKEEPER_CONNECT
      value: "zookeeper:2181"
    - name: KAFKA_ADVERTISED_PORT
      value: "9092"
    - name: KAFKA_DELETE_TOPIC_ENABLE
      value: "true"
    - name: KAFKA_CREATE_TOPICS
      value: "tpinput:1:1,tpoutput:1:1,operinput:1:1,operoutput:1:1,authoutput:1:1"  
    - name: KAFKA_JMX_PORT
      value: "7071"             
    - name: KAFKA_ZOOKEEPER_TIMEOUT_MS
      value: "16000"
    - name: KAFKA_MESSAGE_MAX_BYTES
      value: "209715200"
    - name: KAFKA_FETCH_MESSAGE_MAX_BYTES
      value: "209715200"  
    - name: KAFKA_REPLICA_FETCH_MAX_BYTES
      value: "209715200" 
    - name: KAFKA_PRODUCER_MAX_REQUEST_SIZE
      value: "9651322321"
    - name: KAFKA_ADVERTISED_HOST_NAME
      valueFrom:
        fieldRef:
          fieldPath: status.podIP        
    - name: KUBE_POD_NAME
      valueFrom:
        fieldRef:
          fieldPath: metadata.name
    imagePullPolicy: Always
    restartPolicy: Always
    envFrom:
    - configMapRef:
        name: env-config-for-pods

最佳答案

基于Docker入口点脚本here和该文件中的这一部分:

EXCLUSIONS="|KAFKA_VERSION|KAFKA_HOME|KAFKA_DEBUG|KAFKA_GC_LOG_OPTS|KAFKA_HEAP_OPTS|KAFKA_JMX_OPTS|KAFKA_JVM_PERFORMANCE_OPTS|KAFKA_LOG|KAFKA_OPTS|"

# Read in env as a new-line separated array. This handles the case of env variables have spaces and/or carriage returns. See #313
IFS=$'\n'
for VAR in $(env)
do
    env_var=$(echo "$VAR" | cut -d= -f1)
    if [[ "$EXCLUSIONS" = *"|$env_var|"* ]]; then
        echo "Excluding $env_var from broker config"
        continue
    fi

    if [[ $env_var =~ ^KAFKA_ ]]; then
        kafka_name=$(echo "$env_var" | cut -d_ -f2- | tr '[:upper:]' '[:lower:]' | tr _ .)
        updateConfig "$kafka_name" "${!env_var}" "$KAFKA_HOME/config/server.properties"
    fi

    if [[ $env_var =~ ^LOG4J_ ]]; then
        log4j_name=$(echo "$env_var" | tr '[:upper:]' '[:lower:]' | tr _ .)
        updateConfig "$log4j_name" "${!env_var}" "$KAFKA_HOME/config/log4j.properties"
    fi
done
KAFKA_MAX_REQUEST_SIZE应该作为$KAFKA_HOME/config/server.properties包含在max.request.size文件中。如果docker镜像中有错误,我不会感到惊讶。

您总是可以将您的Kafka Pod放入 shell 并检查$KAFKA_HOME/config/server.properties配置文件。
kubectl exec -it <kafka-pod> -c <kafka-container> sh

关于kubernetes - Kubernetes中的max.request.size Kafka,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/52662703/

相关文章:

azure - AKS 集群重新启动后 Pod 在不存在的节点上运行

elasticsearch - 在K8s上运行ElasticSearch和Kibana错误-Kibana无法正确加载。检查服务器输出以获取更多信息

dns - Kubernetes 服务发现无法解析 minikube 上的服务主机

kubernetes - Prometheus 查询 pod 内存使用性能分位数

java - Apache Samza 不运行

apache-kafka - 共享 Kafka StateStore 最佳实践

apache-kafka - Kafka 单个消费者在一个组中失败

kubernetes - 优雅的 Pod 终止

ssl - kafka - ssl握手失败

performance - 请求/响应的 Kafka 消息时间戳