You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jœl Salmerón Viver (JIRA)" <ji...@apache.org> on 2018/12/12 17:32:01 UTC
[jira] [Comment Edited] (KAFKA-2729) Cached zkVersion not equal to
that in zookeeper, broker not recovering.
[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719147#comment-16719147 ]
Jœl Salmerón Viver edited comment on KAFKA-2729 at 12/12/18 5:31 PM:
---------------------------------------------------------------------
[~junrao], this issue is not yet fixed it seems. We, as others here, are experiencing the same loop replication of partitions when trying to delete topics via the bin/kakfa-topics command using 1.1 brokers.
If fixed as you say, could someone update the exact broker version where it is fixed?
If am torn to upgrade to 2.2 on the brokers, as this bug report does not reflect what you imply by your "We fixed another issue" - that is, assuming the issue is fixed - comment above.
was (Author: murri71):
[~junrao], this issue is not yet fixed it seems. We, as others here, are experiencing the same loop replication of partitions when trying to delete topics via the bin/kakfa-topics command using 1.1 brokers.
If fixed as you say, could someone update the exact broker version where it is fixed?
If am torn to upgrade to 2.2 on the brokers, as this bug report does not reflect what you imply by your "We fixed another issue" comment above.
> Cached zkVersion not equal to that in zookeeper, broker not recovering.
> -----------------------------------------------------------------------
>
> Key: KAFKA-2729
> URL: https://issues.apache.org/jira/browse/KAFKA-2729
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1, 0.9.0.0, 0.10.0.0, 0.10.1.0, 0.11.0.0
> Reporter: Danil Serdyuchenko
> Assignee: Onur Karaman
> Priority: Major
> Fix For: 1.1.0
>
>
> After a small network wobble where zookeeper nodes couldn't reach each other, we started seeing a large number of undereplicated partitions. The zookeeper cluster recovered, however we continued to see a large number of undereplicated partitions. Two brokers in the kafka cluster were showing this in the logs:
> {code}
> [2015-10-27 11:36:00,888] INFO Partition [__samza_checkpoint_event-creation_1,3] on broker 5: Shrinking ISR for partition [__samza_checkpoint_event-creation_1,3] from 6,5 to 5 (kafka.cluster.Partition)
> [2015-10-27 11:36:00,891] INFO Partition [__samza_checkpoint_event-creation_1,3] on broker 5: Cached zkVersion [66] not equal to that in zookeeper, skip updating ISR (kafka.cluster.Partition)
> {code}
> For all of the topics on the effected brokers. Both brokers only recovered after a restart. Our own investigation yielded nothing, I was hoping you could shed some light on this issue. Possibly if it's related to: https://issues.apache.org/jira/browse/KAFKA-1382 , however we're using 0.8.2.1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)