[jira] [Created] (KAFKA-6320) move ZK metrics in KafkaHealthCheck to ZookeeperClient

Jun Rao created KAFKA-6320: -- Summary: move ZK metrics in KafkaHealthCheck to ZookeeperClient Key: KAFKA-6320 URL: https://issues.apache.org/jira/browse/KAFKA-6320 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-6065) Add zookeeper metrics to ZookeeperClient as in KIP-188

[ https://issues.apache.org/jira/browse/KAFKA-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-6065: -- Assignee: Ismael Juma (was: Prasanna Gautam) > Add zookeeper metrics to ZookeeperClient as in KIP-188

[jira] [Commented] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267123#comment-16267123 ] Jun Rao commented on KAFKA-1120: [~mimaison], thanks for helping out! > Controller could miss a broker

[jira] [Commented] (KAFKA-6194) Server crash while deleting segments

[ https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254671#comment-16254671 ] Jun Rao commented on KAFKA-6194: [~corlettb], if the compaction is very aggressive, it is possible that a

[jira] [Commented] (KAFKA-6194) Server crash while deleting segments

[ https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249855#comment-16249855 ] Jun Rao commented on KAFKA-6194: [~corlettb], thanks for the info. As Ismael mentioned, there was a

[jira] [Commented] (KAFKA-6194) Server crash while deleting segments

[ https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248602#comment-16248602 ] Jun Rao commented on KAFKA-6194: [~corlettb], thanks for the info. It seems that the deletion failure

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248033#comment-16248033 ] Jun Rao commented on KAFKA-5473: [~prasincs], thanks. Another thing that I mentioned in the PR is that it

[jira] [Commented] (KAFKA-6194) Server crash while deleting segments

[ https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247824#comment-16247824 ] Jun Rao commented on KAFKA-6194: [~corlettb], thanks for the info. You may want to restart the broker

[jira] [Commented] (KAFKA-6194) Server crash while deleting segments

[ https://issues.apache.org/jira/browse/KAFKA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16246938#comment-16246938 ] Jun Rao commented on KAFKA-6194: In 1.0.0, because of KIP-112, the handling of IOException is a bit

[jira] [Commented] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244270#comment-16244270 ] Jun Rao commented on KAFKA-6184: [~huxi_2b], thanks for your the patch. Since this is a public facing

[jira] [Created] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

Jun Rao created KAFKA-6184: -- Summary: report a metric of the lag between the consumer offset and the start offset of the log Key: KAFKA-6184 URL: https://issues.apache.org/jira/browse/KAFKA-6184 Project:

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241272#comment-16241272 ] Jun Rao commented on KAFKA-5473: [~prasincs], thanks. I think the existing zk state metric is probably

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240928#comment-16240928 ] Jun Rao commented on KAFKA-5473: [~prasincs], after the discussion in KIP-217, we decided not to expose a

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226013#comment-16226013 ] Jun Rao commented on KAFKA-4084: [~jeffwidman], the detailed perf results can be found in

[jira] [Updated] (KAFKA-5647) Use async ZookeeperClient for Admin operations

[ https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5647: --- Description: Since we will be removing the ZK dependency in most of the admin clients, we only need to change

[jira] [Updated] (KAFKA-5647) Use async ZookeeperClient for Admin operations

[ https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5647: --- Description: Since we will be removing the ZK dependency in most of the admin clients, we only need to change

[jira] [Comment Edited] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225767#comment-16225767 ] Jun Rao edited comment on KAFKA-4084 at 10/30/17 9:30 PM: -- The auto leader

[jira] [Resolved] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-4084. Resolution: Fixed Fix Version/s: 1.1.0 The auto leader balancing logic now uses the async ZK api and

[jira] [Assigned] (KAFKA-3018) Kafka producer hangs on producer.close() call if the producer topic contains single quotes in the topic name

[ https://issues.apache.org/jira/browse/KAFKA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-3018: -- Assignee: (was: Jun Rao) > Kafka producer hangs on producer.close() call if the producer topic

[jira] [Commented] (KAFKA-6146) re-register the exist watch on PreferredReplicaElectionZNode after the preferred leader election completes

[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225449#comment-16225449 ] Jun Rao commented on KAFKA-6146: We can fix this in a way similar to

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222990#comment-16222990 ] Jun Rao commented on KAFKA-5473: [~prasincs], I created

[jira] [Commented] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

[ https://issues.apache.org/jira/browse/KAFKA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216276#comment-16216276 ] Jun Rao commented on KAFKA-6074: [~tedyu], thanks for the patch. A couple of comments. 1. You don't need

[jira] [Commented] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

[ https://issues.apache.org/jira/browse/KAFKA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216185#comment-16216185 ] Jun Rao commented on KAFKA-6074: [~tedyu], that's right. > Use ZookeeperClient in ReplicaManager and

[jira] [Commented] (KAFKA-5027) Kafka Controller Redesign

[ https://issues.apache.org/jira/browse/KAFKA-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216153#comment-16216153 ] Jun Rao commented on KAFKA-5027: For the 1.1.0 release, we want to be able to complete at least the

[jira] [Commented] (KAFKA-6094) transient failure in testMultipleMarkersOneLeader

[ https://issues.apache.org/jira/browse/KAFKA-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213698#comment-16213698 ] Jun Rao commented on KAFKA-6094: This is one of the two test failures in that run. > transient failure

[jira] [Commented] (KAFKA-6098) Delete and Re-create topic operation could result in race condition

[ https://issues.apache.org/jira/browse/KAFKA-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212883#comment-16212883 ] Jun Rao commented on KAFKA-6098: The reason for deleting the topic path first and then the topic deletion

[jira] [Resolved] (KAFKA-6071) Use ZookeeperClient in LogManager

[ https://issues.apache.org/jira/browse/KAFKA-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-6071. Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4089

[jira] [Commented] (KAFKA-6094) transient failure in testMultipleMarkersOneLeader

[ https://issues.apache.org/jira/browse/KAFKA-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212036#comment-16212036 ] Jun Rao commented on KAFKA-6094: cc [~apurva] and [~hachikuji] > transient failure in

[jira] [Created] (KAFKA-6094) transient failure in testMultipleMarkersOneLeader

Jun Rao created KAFKA-6094: -- Summary: transient failure in testMultipleMarkersOneLeader Key: KAFKA-6094 URL: https://issues.apache.org/jira/browse/KAFKA-6094 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-6093) replica dir not deleted after topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-6093: --- Fix Version/s: 1.0.0 > replica dir not deleted after topic deletion >

[jira] [Commented] (KAFKA-6093) replica dir not deleted after topic deletion

[ https://issues.apache.org/jira/browse/KAFKA-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212016#comment-16212016 ] Jun Rao commented on KAFKA-6093: This seem to happen only in the 1.0 branch. The issue seems to be that in

[jira] [Created] (KAFKA-6093) replica dir not deleted after topic deletion

Jun Rao created KAFKA-6093: -- Summary: replica dir not deleted after topic deletion Key: KAFKA-6093 URL: https://issues.apache.org/jira/browse/KAFKA-6093 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3083. Resolution: Fixed Assignee: Onur Karaman (was: Mayuresh Gharat) Fix Version/s: 1.1.0 This

[jira] [Resolved] (KAFKA-3038) Speeding up partition reassignment after broker failure

[ https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3038. Resolution: Duplicate This is now fixed in KAFKA-5642. > Speeding up partition reassignment after broker

[jira] [Resolved] (KAFKA-4444) Aggregate requests sent from controller to broker during controlled shutdown

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-. Resolution: Duplicate This is now fixed in KAFKA-5642. > Aggregate requests sent from controller to broker

[jira] [Assigned] (KAFKA-6051) ReplicaFetcherThread should close the ReplicaFetcherBlockingSend earlier on shutdown

[ https://issues.apache.org/jira/browse/KAFKA-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-6051: -- Assignee: Maytee Chinavanichkit > ReplicaFetcherThread should close the ReplicaFetcherBlockingSend

[jira] [Resolved] (KAFKA-5642) Use async ZookeeperClient in Controller

[ https://issues.apache.org/jira/browse/KAFKA-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5642. Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 3765

[jira] [Updated] (KAFKA-5647) Use async ZookeeperClient for Admin operations

[ https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5647: --- Description: This includes ConfigCommand, ZkSecurityMigrator, ExportZkOffsets, ImportZkOffsets,

[jira] [Updated] (KAFKA-5646) Use async ZookeeperClient for DynamicConfigManager

[ https://issues.apache.org/jira/browse/KAFKA-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5646: --- Affects Version/s: 1.1.0 Fix Version/s: 1.1.0 Description: We want to replace the usage of

[jira] [Created] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

Jun Rao created KAFKA-6074: -- Summary: Use ZookeeperClient in ReplicaManager and Partition Key: KAFKA-6074 URL: https://issues.apache.org/jira/browse/KAFKA-6074 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-6073) Use ZookeeperClient in KafkaApis

Jun Rao created KAFKA-6073: -- Summary: Use ZookeeperClient in KafkaApis Key: KAFKA-6073 URL: https://issues.apache.org/jira/browse/KAFKA-6073 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-6072) Use ZookeeperClient in GroupCoordinator and TransactionCoordinator

[ https://issues.apache.org/jira/browse/KAFKA-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-6072: --- Summary: Use ZookeeperClient in GroupCoordinator and TransactionCoordinator (was: Use ZookeeperClient in

[jira] [Created] (KAFKA-6071) Use ZookeeperClient in LogManager

Jun Rao created KAFKA-6071: -- Summary: Use ZookeeperClient in LogManager Key: KAFKA-6071 URL: https://issues.apache.org/jira/browse/KAFKA-6071 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-5871) bound the throttle time in byte rate quota

[ https://issues.apache.org/jira/browse/KAFKA-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206904#comment-16206904 ] Jun Rao commented on KAFKA-5871: I posted the following in a related jira KAFKA-6028. With a reduced

[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=16204367#comment-16204367 ] Jun Rao commented on KAFKA-2729: [~fravigotti], sorry to hear that. A couple of quick suggestions. (1) Do

[jira] [Commented] (KAFKA-5663) LogDirFailureTest system test fails

[ https://issues.apache.org/jira/browse/KAFKA-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204151#comment-16204151 ] Jun Rao commented on KAFKA-5663: Not sure. The test fails with the following error. 07:56:28 Broker 2

[jira] [Commented] (KAFKA-5663) LogDirFailureTest system test fails

[ https://issues.apache.org/jira/browse/KAFKA-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203991#comment-16203991 ] Jun Rao commented on KAFKA-5663: [~lindong], I was running the system test for the controller improvement

[jira] [Commented] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

[ https://issues.apache.org/jira/browse/KAFKA-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199794#comment-16199794 ] Jun Rao commented on KAFKA-6029: [~becket_qin], yes, that's the rough idea. > Controller should wait for

[jira] [Commented] (KAFKA-6028) Improve the quota throttle communication.

[ https://issues.apache.org/jira/browse/KAFKA-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199792#comment-16199792 ] Jun Rao commented on KAFKA-6028: [~becket_qin], the window size is configurable and we can reduce the

[jira] [Commented] (KAFKA-6028) Improve the quota throttle communication.

[ https://issues.apache.org/jira/browse/KAFKA-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199316#comment-16199316 ] Jun Rao commented on KAFKA-6028: Another way to address this is what's described in

[jira] [Commented] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

[ https://issues.apache.org/jira/browse/KAFKA-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199314#comment-16199314 ] Jun Rao commented on KAFKA-6029: One of the issues that can lead to this is that the follower and the

[jira] [Commented] (KAFKA-5140) Flaky ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198036#comment-16198036 ] Jun Rao commented on KAFKA-5140: Saw the following transient failures in a recent PR builder.

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192247#comment-16192247 ] Jun Rao commented on KAFKA-5473: The PR is in https://github.com/apache/kafka/pull/3990. We agreed to fix

[jira] [Resolved] (KAFKA-5767) Kafka server should halt if IBP < 1.0.0 and there is log directory failure

[ https://issues.apache.org/jira/browse/KAFKA-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5767. Resolution: Fixed Issue resolved by pull request 3718 [https://github.com/apache/kafka/pull/3718] > Kafka

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190609#comment-16190609 ] Jun Rao commented on KAFKA-5758: [~dwvangeest], thanks for the info. > Reassigning a topic's partitions

[jira] [Resolved] (KAFKA-5995) Rename AlterReplicaDir to AlterReplicaDirs

[ https://issues.apache.org/jira/browse/KAFKA-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5995. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3993

[jira] [Commented] (KAFKA-5758) Reassigning a topic's partitions can adversely impact other topics

[ https://issues.apache.org/jira/browse/KAFKA-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188465#comment-16188465 ] Jun Rao commented on KAFKA-5758: [~dwvangeest], thanks for the info. I agree that it's better to handle

[jira] [Created] (KAFKA-5871) bound the throttle time in byte rate quota

Jun Rao created KAFKA-5871: -- Summary: bound the throttle time in byte rate quota Key: KAFKA-5871 URL: https://issues.apache.org/jira/browse/KAFKA-5871 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5858) consumer.poll() shouldn't throw exception due to deserialization error

[ https://issues.apache.org/jira/browse/KAFKA-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157902#comment-16157902 ] Jun Rao commented on KAFKA-5858: [~hachikuji], any caveats for doing this? > consumer.poll() shouldn't

[jira] [Commented] (KAFKA-3039) Temporary loss of leader resulted in log being completely truncated

[ https://issues.apache.org/jira/browse/KAFKA-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157087#comment-16157087 ] Jun Rao commented on KAFKA-3039: Hmm, interesting. Not sure why this is happening. Currently, when a

[jira] [Commented] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142400#comment-16142400 ] Jun Rao commented on KAFKA-1120: Yes, that's the right metric. The only down side of increasing the

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140402#comment-16140402 ] Jun Rao commented on KAFKA-5781: The metrics are described in

[jira] [Commented] (KAFKA-5781) Frequent long produce latency periods that result in reduced produce rate.

[ https://issues.apache.org/jira/browse/KAFKA-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140278#comment-16140278 ] Jun Rao commented on KAFKA-5781: It would also be useful to know the producer latency breakdown on the

[jira] [Commented] (KAFKA-5745) Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader

[ https://issues.apache.org/jira/browse/KAFKA-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129725#comment-16129725 ] Jun Rao commented on KAFKA-5745: The HW in the follower only includes the offset, but not the log segment

[jira] [Created] (KAFKA-5745) Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader

Jun Rao created KAFKA-5745: -- Summary: Partition.makeLeader() should convert HW to OffsetMetadata before becoming the leader Key: KAFKA-5745 URL: https://issues.apache.org/jira/browse/KAFKA-5745 Project:

[jira] [Resolved] (KAFKA-3984) Broker doesn't retry reconnecting to an expired Zookeeper connection

[ https://issues.apache.org/jira/browse/KAFKA-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3984. Resolution: Duplicate Marking this as duplicate. The fix will be done in KAFKA-5473. > Broker doesn't

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125827#comment-16125827 ] Jun Rao commented on KAFKA-5473: [~braedon], yes, this is the same issue as described in KAFKA-3984. >

[jira] [Created] (KAFKA-5706) log the name of the error instead of the error code in response objects

Jun Rao created KAFKA-5706: -- Summary: log the name of the error instead of the error code in response objects Key: KAFKA-5706 URL: https://issues.apache.org/jira/browse/KAFKA-5706 Project: Kafka

[jira] [Resolved] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5501. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3427

[jira] [Resolved] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5431. Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request 3525

[jira] [Commented] (KAFKA-5542) Improve Java doc for LeaderEpochFileCache.endOffsetFor()

[ https://issues.apache.org/jira/browse/KAFKA-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16069126#comment-16069126 ] Jun Rao commented on KAFKA-5542: We can clarify the following. "During the upgrade phase when some

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063437#comment-16063437 ] Jun Rao commented on KAFKA-5473: [~prasincs], there are a couple cases to consider. (1) This is the case

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063228#comment-16063228 ] Jun Rao commented on KAFKA-5413: Merged https://github.com/apache/kafka/pull/3397 to 0.10.2. > Log

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061578#comment-16061578 ] Jun Rao commented on KAFKA-5473: We could retry up to zk.connection.time.ms and then give up. > handle ZK

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060973#comment-16060973 ] Jun Rao commented on KAFKA-5473: [~prasincs], yes, the simplest solution is for the broker to exit on

[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=16060110#comment-16060110 ] Jun Rao commented on KAFKA-2729: [~timoha], we are trying to address the ZK session expiration issue in

[jira] [Resolved] (KAFKA-5491) The ProducerPerformance tool should support transactions

[ https://issues.apache.org/jira/browse/KAFKA-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5491. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3400

[jira] [Assigned] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-5413: -- Assignee: Kelvin Rutt > Log cleaner fails due to large offset in segment file >

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054960#comment-16054960 ] Jun Rao commented on KAFKA-5473: Yes, the issue is there since KAFKA-2405 was committed. So, it's

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054757#comment-16054757 ] Jun Rao commented on KAFKA-5473: The simplest solution is to just fail the broker if the new ZK session

[jira] [Created] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

Jun Rao created KAFKA-5473: -- Summary: handle ZK session expiration properly when a new session can't be established Key: KAFKA-5473 URL: https://issues.apache.org/jira/browse/KAFKA-5473 Project: Kafka

<    1   2   3   4   5