Hello,

Could you try to check your zookeeper log to see if the topic has been
successfully created and the broker has been selected by the controller to
be the leader of this topic? The log entry should be something like

Broker %d handling LeaderAndIsr request correlation id ...

BTW from your logs the server only successfully elect as the controller in
06:30 while the producer's exceptions are in 06:13, so could you check in
the kafka-controller log to see if the server elected itself as the
controller before 06:13? The log entry should be something like

Broker %d starting become controller state transition ...

Guozhang


On Thu, Oct 10, 2013 at 3:53 PM, wangxu <sacat...@gmail.com> wrote:

>  Hi,
>
> Following the *kafka 
> documentation*<http://kafka.apache.org/documentation.html#quickstart>,
> I succeeded in Step 1: Download the code, Step 2: Start the server and Step
> 3: Create a topic in three different terminals.
> While I tried Step 4: Send some messages, the problem happened, the
> producer for the topic "test" could be started, however, I got an exception
> in the producer console (the fourth terminal) after I sent "This is a
> message" in the producer console. The exception looks like
> :"kafka.common.FailedToSendMessageException: Failed to send messages after
> 3 tries."
> I put the detail information to the attachment "producer_terminal.log".
> The attachement "server.log.2013-10-11-05" keeps a piece of information
> about java.net.ConnectException that seems to be the key of the problem.
> But I have no idea how this can happen.
>
> I also tried to have a consumer connecting to the topic ready before
> sending the message in producer terminal, the problem was the same.
>
> My environment:
> CentOS 6.4 (x64), kafka-0.8.0-beta1-src, jdk 1.6.0_31
>
> Can anyone help? Thanks in advance.
>
> Best regards,
>
> WangXu(Alvin)
>



-- 
-- Guozhang

Reply via email to