Build failed in Jenkins: kafka-trunk-jdk8 #2299

See Changes: [jason] MINOR: Use TopicPartition in ConsumerGroupCommand instead of -- [...truncated 399.82 KB...] kafka.utils.CoreUtilsTest > testReadInt STARTED kafka.ut

Re: [DISCUSS] KIP-232: Detect outdated metadata by adding ControllerMetadataEpoch field

Hi, Dong, Thanks for the updated KIP. Still have some questions on the latest approach in the KIP. Consider the following scenario. In metadata v1, the leader for a partition is at broker 1. In metadata v2, leader is at broker 2. In metadata v3, leader is at broker 1 again. The last committed off

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hi, Tom, Thanks for the reply. 10. That's a good thought. Perhaps it's better to get rid of /admin/reassignment_requests too. The window when a controller is not available is small. So, we can just failed the admin client if the controller is not reachable after the timeout. 13. With the changes

Re: [DISCUSS] KIP-227: Introduce Incremental FetchRequests to Increase Partition Scalability

>> >> The point I want to make is that avoiding doing binary search on index >> file and avoid reading the log segments during fetch has some additional >> benefits. So if the solution works for the current KIP, it might be a >> better choice. >Let's discuss this in a follow-on KIP. If the discus

[jira] [Created] (KAFKA-6399) Consider reducing "max.poll.interval.ms" default for Kafka Streams

Matthias J. Sax created KAFKA-6399: -- Summary: Consider reducing "max.poll.interval.ms" default for Kafka Streams Key: KAFKA-6399 URL: https://issues.apache.org/jira/browse/KAFKA-6399 Project: Kafka

Jenkins build is back to normal : kafka-trunk-jdk7 #3061

See

[jira] [Resolved] (KAFKA-5772) Improve Util classes

[ https://issues.apache.org/jira/browse/KAFKA-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5772. Resolution: Fixed Fix Version/s: 1.1.0 > Improve Util classes >

[jira] [Resolved] (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:all-tabpanel ] Ismael Juma resolved KAFKA-2729. Resolution: Fixed Assignee: Onur Karaman Fix Version/s: 1.1.0 We believe this is fix

Re: Question Kafka Reassign partitions tool

Yes, the replicas are stored in Zookeeper, so you can iterate over the information there to build a view of the cluster that you can use. If you want an example for this, take a look at the code for kafka-assigner in https://github.com/linkedin/kafka-tools. Or you can just use that tool to adjust r

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hi Jun, Thanks for responding, my replies are inline: 10. You explanation makes sense. My remaining concern is the additional ZK > writes in the proposal. With the proposal, we will need to do following > writes in ZK. > > a. write new assignment in /admin/reassignment_requests > > b. write new a

Re: [DISCUSS] KIP-240: AdminClient.listReassignments AdminClient.describeReassignments

Hi Steven, I must admit that I didn't really considered that option. I can see how attractive it is from your perspective. In practice it would come with lots of edge cases which would need to be thought through: 1. What happens if the controller can't produce a record to this topic because the p

Re: Question Kafka Reassign partitions tool

Hi Todd, Thanks for the reply. Problem is I have about 160 topics(5 partitions for each) for which I need to increase the replication factors for. So, I would have to find the current leader for each of the partitions and hand code the json which would become tedious. The partition leader info is

Re: Question Kafka Reassign partitions tool

Preferred replica election is naive. It will always follow the order of the replicas as they are set. So if you want to set the default leader, just make it the first replica in the list for the partition. We build the JASON this way all the time. -Todd On Dec 22, 2017 6:46 AM, "Sagar" wrote:

Jenkins build is back to normal : kafka-trunk-jdk8 #2295

See

Build failed in Jenkins: kafka-0.10.1-jdk7 #130

See -- [...truncated 593.55 KB...] org.apache.kafka.streams.processor.internals.StreamsMetadataStateTest > shouldReturnEmptyCollectionOnGetAllInstancesWithStoreWhenStoreDoesntExist STAR

Build failed in Jenkins: kafka-0.10.2-jdk7 #200

See -- [...truncated 326.91 KB...] kafka.coordinator.GroupMetadataTest > testInitNextGenerationEmptyGroup STARTED kafka.coordinator.GroupMetadataTest > testInitNextGenerationEmptyGroup

Build failed in Jenkins: kafka-trunk-jdk7 #3060

See Changes: [github] KAFKA-6320: Move ZK metrics in KafkaHealthCheck to ZookeeperClient -- [...truncated 400.28 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCom

Question Kafka Reassign partitions tool

Hi, Had a question on Kafka reassign partitions tool. We have a 3 node cluster but our replication factor is set to 1. So we have been looking to increase it to 3 for HA. I tried the tool on a couple of topics and it increases the replication factor alright. Also it doesn't change the leader as

Jenkins build is back to normal : kafka-0.10.0-jdk7 #215

See

Jenkins build is back to normal : kafka-0.11.0-jdk7 #346

See

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

[ https://issues.apache.org/jira/browse/KAFKA-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6320. Resolution: Fixed > move ZK metrics in KafkaHealthCheck to ZookeeperClient > ---

[jira] [Resolved] (KAFKA-6380) transient failure in MetricsTest.testMetrics

[ https://issues.apache.org/jira/browse/KAFKA-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6380. -- Resolution: Won't Fix Related code is getting changed in KAFKA-6320. > transient failure in MetricsTe