[jira] [Commented] (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=15879554#comment-15879554 ] Kane Kim commented on KAFKA-2729: - In my opinion it doesn't matter what's

[jira] [Commented] (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=15412359#comment-15412359 ] Kane Kim commented on KAFKA-2729: - For us the reason was high percentage of lost pac

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402962#comment-15402962 ] Kane Kim commented on KAFKA-3042: - We've found it's also being triggered

[jira] [Commented] (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=15395953#comment-15395953 ] Kane Kim commented on KAFKA-2729: - This is hitting us badly on kafka 0.10.0.0, it doe

[jira] [Commented] (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=15261189#comment-15261189 ] Kane Kim commented on KAFKA-2729: - Same problem with the same symptoms occurred on k

[jira] [Commented] (KAFKA-1382) Update zkVersion on partition state update failures

[ https://issues.apache.org/jira/browse/KAFKA-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261182#comment-15261182 ] Kane Kim commented on KAFKA-1382: - We've been hitting this bug too on kafk

mirror maker and failover to another data center

Hello, What's the best strategy for failover when using mirror-maker to replicate across datacenters? As I understand offsets in both datacenters will be different, how consumers should be reconfigured to continue reading from the same point where they stopped without data loss and/or duplication?

controller conflict

Hello, We are using kafka 0.8.1.1 and hit this bug - 1029, /controller ephemeral node conflict. Is it supposed to be fixed or has something to do with 1451? Thanks.

[jira] [Updated] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim updated KAFKA-1116: Fix Version/s: 0.8.1 0.8 Labels: build (was: ) Affects

[jira] [Updated] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim updated KAFKA-1116: Attachment: kafka-1116-scala.2.10.2.patch Upgrading sbt-assembly > Need to upgrade sbt-assembly

[jira] [Reopened] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim reopened KAFKA-1116: - Attaching a patch > Need to upgrade sbt-assembly to compile on scala 2.1

[jira] [Resolved] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

[ https://issues.apache.org/jira/browse/KAFKA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kane Kim resolved KAFKA-1116. - Resolution: Implemented > Need to upgrade sbt-assembly to compile on scala 2.1

[jira] [Created] (KAFKA-1116) Need to upgrade sbt-assembly to compile on scala 2.10.2

Kane Kim created KAFKA-1116: --- Summary: Need to upgrade sbt-assembly to compile on scala 2.10.2 Key: KAFKA-1116 URL: https://issues.apache.org/jira/browse/KAFKA-1116 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-1112) broker can not start itself after kafka is killed with -9

Kane Kim created KAFKA-1112: --- Summary: broker can not start itself after kafka is killed with -9 Key: KAFKA-1112 URL: https://issues.apache.org/jira/browse/KAFKA-1112 Project: Kafka Issue Type