Nope. You should upgrade to Kafka 0.9, assuming that your
ActiveControllerCount across all brokers is 0 or more than 1 (which is
typically the failure case we see).
Thanks
Tom Crayford
Heroku Kafka
On Wed, Jun 1, 2016 at 3:22 AM, Fredo Lee wrote:
> we use 0.8.2.2. is this version ok?
>
> 2016-
we use 0.8.2.2. is this version ok?
2016-05-31 20:12 GMT+08:00 Tom Crayford :
> Hi,
>
> Which version of Kafka are you running? We run thousands of clusters, and
> typically use this mechanism for replacing damaged hardware, and we've only
> seen this issue under Kafka 0.8, where the controller c
Hi,
Which version of Kafka are you running? We run thousands of clusters, and
typically use this mechanism for replacing damaged hardware, and we've only
seen this issue under Kafka 0.8, where the controller can get stuck (due to
a few bugs in Kafka) and not be functioning. If you are on 0.8, I'd
i find the new broker with old broker id always fetch message from itself
for the reason that it believe it's the leader of some partitions.
2016-05-31 15:56 GMT+08:00 Fredo Lee :
> we have a kafka cluster and one of them is down for the reason of disk
> damaged. so we use the same broker id in a
