Hi,
I don’t have experience running Kafka clusters behind proxies, but it seems
like the configurations “advertised.host.name” and “advertised.port” for your
Kafka brokers are what you’re looking for.
For information on that please refer to the Kafka documentations.
Cheers,
Gordon
On 12 Augus
It is solvable? I'm not an expert of this stuff and the cluster is managed by
the lab responsible. Maybe I can ask him to do something in order to solve.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Error-during-Kafka-connection-tp14822p14
Hi,
You mentioned that your kafka broker is behind a proxy. This could be a
problem, because when the client try to get the cluster's topology, it will get
the brokers ' private addresses , which is not reachable.
Regards,
Kien
On Aug 11, 2017, 18:18, at 18:18, "Tzu-Li (Gordon) Tai"
wrote:
I just tried to use telnet to public ip:port from outside and it works.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Error-during-Kafka-connection-tp14822p14829.html
Sent from the Apache Flink User Mailing List archive. mailing list archiv
I tried running console consumer-producer from the localhost on the cluster:
this say me that the broker is currently active.
To reach the cluster from outside I use a redirect from a public (ip, port),
because the ip of the kafka broker is private... I suspect the problem can
be there.
--
View
No, there should be no difference between setting it up on Ubuntu or OS X.
I can’t really tell any anything suspicious from the information provided so
far, unfortunately.
Perhaps you can try first checking that the Kafka topic is consumable from
where you’re running Flink, e.g. using the exampl
the kafka version I use is the latest (0.11.0.0). But to be honestly, also
locally I use 0.11.0.0 and in that case it works correctly. Anyway the last
kafka connector on flink is designed for kafka 0.10.x.x
I use OS X locally and Ubuntu on the cluster. It has importance?
--
View this message in
Hi,
AFAIK, Kafka group coordinators are supposed to always be marked dead, because
we use static assignment internally and therefore Kafka's group coordination
functionality is disabled.
Though it may be obvious, but to get that out of the way first: are you sure
that the Kafka installation ve
