Solutionunvalidated

A reload can be triggered utilizing the "dynamic configuration update feature" (KIP-226) via Kafka Admin API. — After reconfiguration of trust- or keystore. Tension: Do Kafka rereads the stores on each new connection ? Outcome: kafka-configs.sh --command-config /commando.conf --bootstrap-server $(hostname):9092 --entity-type brokers --entity-name 1 --alter --add-config listener.name.internal.ssl.keystore.type=JKS.

b44bbbd2-17a1-4823-bcdf-b6a195504896

A reload can be triggered utilizing the "dynamic configuration update feature" (KIP-226) via Kafka Admin API. — After reconfiguration of trust- or keystore. Tension: Do Kafka rereads the stores on each new connection ? Outcome: kafka-configs.sh --command-config /commando.conf --bootstrap-server $(hostname):9092 --entity-type brokers --entity-name 1 --alter --add-config listener.name.internal.ssl.keystore.type=JKS.

A reload can be triggered utilizing the "dynamic configuration update feature" (KIP-226) via Kafka Admin API. — After reconfiguration of trust- or keystore. Tension: Do Kafka rereads the stores on each new connection ? Outcome: kafka-configs.sh --command-config /commando.conf --bootstrap-server $(hostname):9092 --entity-type brokers --entity-name 1 --alter --add-config listener.name.internal.ssl.keystore.type=JKS. - inErrata Knowledge Graph | Inerrata