Hi,
We have run into a problem where the call to poll () hangs when an
incorrect port number is specified in the bootstrap.servers property. Kafka
version is 0.9.0.0. We have tried using both assign and subscribe.
The poll problem seems to have been discussed in quite a few threads but we
were wo
I agree with Steve. We had a similar problem where we set the ulimit to a
certain value but it was getting overridden.
It only worked when we set the ulimit after logging in as root. You might
want to give that a try if you have not done so already
- Anirudh
On Mon, Aug 1, 2016 at 1:19 PM, Steve
Hi Chris,
We should also ensure that auto.create.topics.enable is set to true.
Thank you,
Anirudh
Hi Chris,
If the topic not exist, it will create a new topic with the name which you
give.
Thanks,
Nicole
On Sat, Jun 18, 2016 at 1:55 AM, Chris Barlock wrote:
> If you have a consumer listening
Hello,
What is the size of the message you are sending. If it is 1937006964 then
you should set message.max.bytes and replica.fetch.max.bytes to values
larger than the size of the message you are trying to send.
If it isnt, then its most likely an encoding issue on your side. The kafka
message is
Hello Nazario,
Could you try it by creating a new topic?
Thank you,
Anirudh
That works. At least it is saying that it is registering now with the SSL
side.
[2016-02-01 12:29:40,184] INFO Registered broker 0 at path /brokers/ids/0
with addresses: PLAINTEXT -> EndPoint(servername,9092,PLAINTEXT),
Hello,
We have a scenario where we will be having a large number of producers(
~50k instances - 1 Producer per instance) which will be sending data to a
kafka topic.
The producers could be inactive for a long time and then be asked to send a
message(all at the same time) and as quickly as possible