The producer is complaining that it's socket channel is already closed.
Which makes me think it was closed due to some error that is not present in
your logs. I'd enable DEBUG and see if that shows the cause.
On Thu, Dec 18, 2014 at 4:13 PM, Gwen Shapira wrote:
>
> Perhaps you have the logs from
Perhaps you have the logs from broker? It may show other errors that
can help us troubleshoot.
On Thu, Dec 18, 2014 at 4:11 PM, Sa Li wrote:
> Thanks, Gwen, I telnet it,
> root@precise64:/etc/kafka# telnet 10.100.98.100 9092
> Trying 10.100.98.100...
> Connected to 10.100.98.100.
> Escape charact
Thanks, Gwen, I telnet it,
root@precise64:/etc/kafka# telnet 10.100.98.100 9092
Trying 10.100.98.100...
Connected to 10.100.98.100.
Escape character is '^]'.
seems it connected, and I check with system operation people, netstate
should 9092 is listening. I am assuming this is the connection issue,
Looks like you can't connect to: 10.100.98.100:9092
I'd validate that this is the issue using telnet and then check the
firewall / ipfilters settings.
On Thu, Dec 18, 2014 at 2:21 PM, Sa Li wrote:
> Dear all
>
> We just build a kafka production cluster, I can create topics in kafka
> production
Dear all
We just build a kafka production cluster, I can create topics in kafka
production from another host. But when I am send very simple message as
producer, it generate such errors:
root@precise64:/etc/kafka# bin/kafka-console-producer.sh --broker-list
10.100.98.100:9092 --topic my-replicate
