[jira] [Commented] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701241#comment-15701241 ] ysysberserk commented on KAFKA-4405: It seems to me that it is not only a performance

[jira] [Commented] (KAFKA-4403) Update KafkaBasedLog to use new endOffsets consumer API

[ https://issues.apache.org/jira/browse/KAFKA-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701240#comment-15701240 ] James Cheng commented on KAFKA-4403: Yay, I like this JIRA. > Update KafkaBasedLog to

[jira] [Commented] (KAFKA-4007) Improve fetch pipelining for low values of max.poll.records

[ https://issues.apache.org/jira/browse/KAFKA-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701234#comment-15701234 ] James Cheng commented on KAFKA-4007: If there is another fetch response on the socket,

Re: [DISCUSS] Deprecating the old consumers in trunk

I like the idea too. Once all the old consumers have upgraded to this new embedded KafkaConsumer and they switch over to the new consumer’s group assignment protocol, does anything change when a real KafkaConsumer joins the group? At this point, if we have say N consumers in the group, we will

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701186#comment-15701186 ] Abhi commented on KAFKA-1194: - SOS please Abhi > The kafka broker cannot delete the old log

[jira] [Commented] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701118#comment-15701118 ] ysysberserk commented on KAFKA-4405: It sounds better, I will check it. But comparing

[jira] [Commented] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701064#comment-15701064 ] Guozhang Wang commented on KAFKA-4405: -- [~enothereska] Maybe this can result in perfo

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701044#comment-15701044 ] ASF GitHub Bot commented on KAFKA-3959: --- GitHub user onurkaraman opened a pull reque

[GitHub] kafka pull request #2177: KAFKA-3959: enforce offsets.topic.replication.fact...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2177 KAFKA-3959: enforce offsets.topic.replication.factor Kafka brokers have a config called "offsets.topic.replication.factor" that specify the replication factor for the "__consumer_offsets" topic.

[jira] [Assigned] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman reassigned KAFKA-3959: --- Assignee: Onur Karaman > __consumer_offsets wrong number of replicas at startup > ---

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700945#comment-15700945 ] Onur Karaman commented on KAFKA-3959: - Awesome. I think we're in agreement? I can impl

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700938#comment-15700938 ] Todd Palino commented on KAFKA-3959: +1 as well. I think keeping the config/server.pro

[jira] [Comment Edited] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700935#comment-15700935 ] Onur Karaman edited comment on KAFKA-3959 at 11/28/16 5:11 AM: -

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700935#comment-15700935 ] Onur Karaman commented on KAFKA-3959: - +1. I was thinking about this approach too (ass

Re: [DISCUSS] Deprecating the old consumers in trunk

Onur's suggestion or something like it sounds like it could work. Suppose we add some metadata in Zookeeper for consumers which support the embedded KafkaConsumer. Until all members in the group have declared support, the consumer will continue use Zk for their partition assignments. But once all m

[jira] [Commented] (KAFKA-4405) Kafka consumer improperly send prefetch request

[ https://issues.apache.org/jira/browse/KAFKA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700704#comment-15700704 ] Jason Gustafson commented on KAFKA-4405: I think a better approach is KAFKA-4007.

[jira] [Commented] (KAFKA-4451) Recovering empty replica yields negative offsets in index of compact partitions

[ https://issues.apache.org/jira/browse/KAFKA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700688#comment-15700688 ] Michael Schiff commented on KAFKA-4451: --- After some further exploration: {code:tit

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700662#comment-15700662 ] Jason Gustafson commented on KAFKA-3959: Could we leave the default at RF=3, but o

[jira] [Updated] (KAFKA-4451) Recovering empty replica yields negative offsets in index of compact partitions

[ https://issues.apache.org/jira/browse/KAFKA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-4451: -- Description: Bringing up an empty broker. the partition for a compact topic is not split into

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700633#comment-15700633 ] Jason Gustafson commented on KAFKA-4447: [~Json Tu] Thanks for the report. I think

[jira] [Created] (KAFKA-4451) Recovering empty replica yields negative offsets in index of compact partitions

Michael Schiff created KAFKA-4451: - Summary: Recovering empty replica yields negative offsets in index of compact partitions Key: KAFKA-4451 URL: https://issues.apache.org/jira/browse/KAFKA-4451 Proje

Re: [DISCUSS] 0.10.1.1 Plan

I guess bugs are in the eye of the beholder; I’d really like to see KAFKA-4438 addressed as a patch release - the bug being "I can’t currently build any scala 2.12 projects with Kafka as a dependency". There’s a PR ready to go for the branch that has already been accepted to trunk and this Isma

[jira] [Commented] (KAFKA-4403) Update KafkaBasedLog to use new endOffsets consumer API

[ https://issues.apache.org/jira/browse/KAFKA-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15699956#comment-15699956 ] ASF GitHub Bot commented on KAFKA-4403: --- GitHub user baluchicken opened a pull reque

[GitHub] kafka pull request #2176: KAFKA-4403 Update KafkaBasedLog to use new endOffs...

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/2176 KAFKA-4403 Update KafkaBasedLog to use new endOffsets consumer API @ewencp plz review You can merge this pull request into a Git repository by running: $ git pull https://github.com/baluchi

[jira] [Work started] (KAFKA-4403) Update KafkaBasedLog to use new endOffsets consumer API

[ https://issues.apache.org/jira/browse/KAFKA-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4403 started by Balint Molnar. > Update KafkaBasedLog to use new endOffsets consumer API > -

Re: A strange controller log in Kafka 0.9.0.1

AnyBody？This is very disconcerting! If convenient, Can somebody help to confirm this strange question. > 在 2016年11月26日，上午1:35，Json Tu 写道： > > thanks guozhang, > if it's convenient，can we disscuss it in the jira > https://issues.apache.org/jira/browse/KAFKA-4447 >

[jira] [Commented] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

[ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15699362#comment-15699362 ] Ismael Juma commented on KAFKA-4450: Ok, the one I filed was about including 0.10.0 as

[jira] [Commented] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

[ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15699339#comment-15699339 ] Ismael Juma commented on KAFKA-4450: Hmm, I filed a JIRA about this before 0.10.1 was