Thanks Matthias for the information!
2017-11-20 19:23 GMT+01:00 Matthias J. Sax :
> Sound like Streams can't fetch the metadata completely.
>
> You can increase Consumer config `REQUEST_TIMEOUT_MS_CONFIG` to give
> more time to the cluster to broadcast the information to all brokers.
>
> https://
O, Kafka. Franz? How are you? Here and there? What is lightbend? This one:
https://www.lightbend.com/?
I had/have cancer. is seems stable now. So for fun I am looking for a job,
elusively remotely one.If you know or happen to heard about one, please send it
to me. I feel mostly pretty well, G
Sound like Streams can't fetch the metadata completely.
You can increase Consumer config `REQUEST_TIMEOUT_MS_CONFIG` to give
more time to the cluster to broadcast the information to all brokers.
https://docs.confluent.io/current/streams/developer-guide/config-streams.html#kafka-consumers-and-prod
Hello,
I am trying to replicate from
consumer: 0.9 using SSL
to producer: 0.11 over non-SSL.
However kafka mirroring always moves to non-ssl as consumer even if i
configure with ssl settings..etc.
Does anyone knows it kafka mirroring in 0.9 works as consumer over ssl?
Thanks,
Andrei
Hello,
We are using Kafka version 0.11.0.1. with KafkaStream.
Using the leftJoin API in the Kafka Stream:
KStream leftJoin(KStream otherStream,
ValueJoiner
joiner,
JoinWindows windows)
https://kafka.apache.org/0110/javadoc/org/apache/kaf
Hello,
I am trying to replicate data from
consumer: 0.9 using SSL
to producer: 0.11 over non-SSL.
However kafka mirroring as consumer always moves to non-ssl as consumer
even if i configure with ssl settings..etc.
Does anyone knows it kafka mirroring in 0.9 works as consumer over ssl?
Thanks
Hello team,
I wanted to know if there is some way I can retrieve consumer properties
from the Kafka Consumer. for example, if at runtime, I want to know the
group id of a particular consumer, in case multiple consumers are running
in my application.
Thanks & Regards,
Simarpreet
Hi Ranjit,
there shouldn't be an issue with having multiple producers, but in general
the preferred approach is to share one producer across multiple threads
(see producer javadoc [1]) as this allows for more efficient pooling of
records and less network overhead.
Kind regards,
Sönke
[1]:
https