You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2018/05/07 05:44:00 UTC

[jira] [Resolved] (KAFKA-6837) Apache kafka broker got stopped.

     [ https://issues.apache.org/jira/browse/KAFKA-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikumar resolved KAFKA-6837.
------------------------------
    Resolution: Information Provided

> Apache kafka broker got stopped.
> --------------------------------
>
>                 Key: KAFKA-6837
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6837
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.11.0.2
>            Reporter: Rajendra Jangir
>            Priority: Major
>
> We are using kafka version 2.11-0.11.0.2 and zookeeper version 3.3.6. And they are they are running on Ubuntu 16.0.4.
> We are producing data with rate of 3k messages per second and the size of each message is around 150 Bytes. we have 7 brokers and 1 zookeeper, and sometimes,  some  brokers get down.
> So how we can find out the reason that why a particular broker was got down? And where the broker stop logs are stored from where we can check the logs and can find why it was stopped?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)