Re: does kafka streams guarantee EOS with external producer used in application?

That's exactly what my question was: since there is an external producer in the application without a sink node in topology, how will the streams know that task is completed before committing the offset or it will not know at all ? Second question is: can there be multiple sink nodes if the

Re: does kafka streams guarantee EOS with external producer used in application?

Yes, if you use async writes, it could lead to data loss in case if failure as offsets could have been committed before the write succeeded. Only sync writes guard you from data loss. Note though that in Kafka Streams there is not manual commit anyway. Commits happen based on `commit.interval.ms`

Re: Kafka 2.7.1 Rebalance failed DisconnectException

Hi Shilin, Thanks for the suggestion. But I am not upgrading an existing cluster. I've got a fresh broker and application cluster and there are no consumer offsets or topics present. When the app starts it creates the topics and once it moves to RUNNING state I see the rebalance failed log every

Re: Apache Kafka 2.8.0 and Zookeeper

Thanks for pointing out the relevant documentation. :) That helps a lot ! On Wed, Jul 14, 2021 at 4:24 AM Shilin Wu wrote: > Kafka 2.8 supports ZooKeeper 3.4.10 through 3.5.9 (3.5.9 recommended). > > According to > >

Re: Option --bootstrap-server not working with kafka-acls.sh or kafka-configs.sh

Hi Use it with --command-config client_security.properties and pass below type configurations in properties file:- sasl.mechanism=PLAIN security.protocol=SASL_SSL sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \ username="*" \ password="*";

Option --bootstrap-server not working with kafka-acls.sh or kafka-configs.sh

Hello to all, I've noticed that when trying to use kafka-acls.sh or kafka-configs.sh by providing the option --bootstrap-server it always leads to the error java.util.concurrent.TimeoutException. The same commands worked without an issue when providing --authorizer-properties

Re: warning messages from kafka admin client

This was fixed in 2.8, see https://issues.apache.org/jira/browse/KAFKA-10090 On Wed, Jul 14, 2021 at 12:19 PM Dhirendra Singh wrote: > Hi All, > whenever i run any kafka CLI tool i am getting following warning messages > > kafka-topics.sh --bootstrap-server kafka-dev:9092 --command-config >

Re: Kafka 2.7.1 Rebalance failed DisconnectException

Depending on your original version, you may have to consult the upgrade guide. https://kafka.apache.org/27/documentation.html#upgrade Didn't see important compatibility settings like: [image: image.png] Perhaps you are not doing it correctly. [image: Confluent] Wu

Re: Apache Kafka 2.8.0 and Zookeeper

Kafka 2.8 supports ZooKeeper 3.4.10 through 3.5.9 (3.5.9 recommended). According to https://docs.confluent.io/platform/current/installation/versions-interoperability.html Note that Confluent Platform 6.2.x is compatible of Kafka 2.8, and Confluent Platform 6.2.x supports ZooKeeper 3.4.10 ~ 3.5.9.

Re: Kafka 2.7.1 Rebalance failed DisconnectException

Can someone help me on this. Thanks, Tony On Fri, Jul 9, 2021 at 8:15 PM Tony John wrote: > Hi All, > > I am trying to upgrade my Kafka streams application to 2.7.1 version of > Kafka. The brokers are upgraded to 2.7.1 and kafka dependencies are also on > 2.7.1. But when I start the

Re: Two doubts about the use of kafka

1. Use something like zk-1:2181:/kafka-root, zk-2:2181:/kafka-root,... 2. You may checkout the jmx monitoring stack using Prometheus and Grafana here . [image: Confluent] Wu Shilin Solution Architect +6581007012

warning messages from kafka admin client

Hi All, whenever i run any kafka CLI tool i am getting following warning messages kafka-topics.sh --bootstrap-server kafka-dev:9092 --command-config client.properties --list [2021-07-14 07:02:31,595] WARN The configuration 'ssl.truststore.location' was supplied but isn't a known config.

Re: does kafka streams guarantee EOS with external producer used in application?

If async-writes are used either with manual or auto commit, where the record is sent for async write and consumer thread commits the offset immediately, however async write fails, this may cause the loss of event ? On Wed, Jul 14, 2021 at 12:20 AM Matthias J. Sax wrote: > If you want to use