[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724000#comment-15724000 ] Jun Rao commented on KAFKA-4454: [~mgharat], I understand the problem that you described.

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742677#comment-15742677 ] Jun Rao commented on KAFKA-4497: [~becket_qin], thanks for providing the fix. The fix seem

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743297#comment-15743297 ] Jun Rao commented on KAFKA-4497: [~becket_qin], it could be. Where do we lose the negative

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743728#comment-15743728 ] Jun Rao commented on KAFKA-4477: [~tdevoe], thanks for sharing the log. On node 1001 and

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743748#comment-15743748 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], the issue that you reported is a

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743756#comment-15743756 ] Jun Rao commented on KAFKA-4497: Got it. I thought Robert was showing the DumpLogSegment o

[jira] [Created] (KAFKA-4529) tombstone may be removed earlier than it should

Jun Rao created KAFKA-4529: -- Summary: tombstone may be removed earlier than it should Key: KAFKA-4529 URL: https://issues.apache.org/jira/browse/KAFKA-4529 Project: Kafka Issue Type: Bug Affects

[jira] [Commented] (KAFKA-4529) tombstone may be removed earlier than it should

[ https://issues.apache.org/jira/browse/KAFKA-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743987#comment-15743987 ] Jun Rao commented on KAFKA-4529: [~becket_qin], do you think you have time to fix this iss

[jira] [Resolved] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-4497. Resolution: Fixed [~roschumann], I merged Jiangjie's batch to 0.10.1 branch. Do you think you could give it

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745782#comment-15745782 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], the 0.10.1.1 release will need R

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745813#comment-15745813 ] Jun Rao commented on KAFKA-4477: [~tdevoe], thanks for the clarification. Then, it looks s

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745817#comment-15745817 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], [~tdevoe], was the following ex

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746393#comment-15746393 ] Jun Rao commented on KAFKA-4477: [~tdevoe], from the controller log, starting from 19:59:1

[jira] [Commented] (KAFKA-4529) tombstone may be removed earlier than it should

[ https://issues.apache.org/jira/browse/KAFKA-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748966#comment-15748966 ] Jun Rao commented on KAFKA-4529: Committed [~becket_qin]'s patch to 0.10.1 branch. Leaving

[jira] [Created] (KAFKA-4545) tombstone needs to be removed after delete.retention.ms has passed after it has been cleaned

Jun Rao created KAFKA-4545: -- Summary: tombstone needs to be removed after delete.retention.ms has passed after it has been cleaned Key: KAFKA-4545 URL: https://issues.apache.org/jira/browse/KAFKA-4545 Projec

[jira] [Commented] (KAFKA-4545) tombstone needs to be removed after delete.retention.ms has passed after it has been cleaned

[ https://issues.apache.org/jira/browse/KAFKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750154#comment-15750154 ] Jun Rao commented on KAFKA-4545: One potential way to fix this is when cleaning a segment

[jira] [Created] (KAFKA-4546) a consumer could miss tombstone when leader changes during the reads

Jun Rao created KAFKA-4546: -- Summary: a consumer could miss tombstone when leader changes during the reads Key: KAFKA-4546 URL: https://issues.apache.org/jira/browse/KAFKA-4546 Project: Kafka Issue

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752252#comment-15752252 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], the deadlock seems to be the sam

[jira] [Updated] (KAFKA-4546) a consumer could miss tombstone when leader changes during the reads

[ https://issues.apache.org/jira/browse/KAFKA-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4546: --- Affects Version/s: 0.10.1.0 This is affecting all versions of Kafka. Not sure what's the best way to address

[jira] [Resolved] (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 ] Jun Rao resolved KAFKA-4451. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 2210 [https://github.com/apa

[jira] [Resolved] (KAFKA-4485) Follower should be in the isr if its FetchRequest has fetched up to the logEndOffset of leader

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

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768759#comment-15768759 ] Jun Rao commented on KAFKA-4277: [~fpj], in KAFKA-1387, you had the following comment: "If

[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=15880817#comment-15880817 ] Jun Rao commented on KAFKA-2729: [~prasincs], if the controller is partitioned off other b

[jira] [Created] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

Jun Rao created KAFKA-4811: -- Summary: ReplicaFetchThread may fail to create due to existing metric Key: KAFKA-4811 URL: https://issues.apache.org/jira/browse/KAFKA-4811 Project: Kafka Issue Type: B

[jira] [Commented] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

[ https://issues.apache.org/jira/browse/KAFKA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887119#comment-15887119 ] Jun Rao commented on KAFKA-4811: In AbstractFetcherManager, we only create a new ReplicaFe

[jira] [Commented] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

[ https://issues.apache.org/jira/browse/KAFKA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888339#comment-15888339 ] Jun Rao commented on KAFKA-4811: [~huxi_2b], yes, we should check both host and port and r

[jira] [Resolved] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

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

[jira] [Commented] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

[ https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898312#comment-15898312 ] Jun Rao commented on KAFKA-4825: [~benstopford], thanks for reporting this. Took a look a

[jira] [Comment Edited] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

[ https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898312#comment-15898312 ] Jun Rao edited comment on KAFKA-4825 at 3/6/17 10:53 PM: - [~bensto

[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=15898415#comment-15898415 ] Jun Rao commented on KAFKA-2729: [~mjuarez], did you see ZK session expiration in the serv

[jira] [Resolved] (KAFKA-4864) Kafka Secure Migrator tool doesn't secure all the nodes

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

[jira] [Commented] (KAFKA-4433) Kafka Controller Does not send a LeaderAndIsr to old leader of a topicPartition during reassignment, if the old leader is not a part of the new assigned replicas

[ https://issues.apache.org/jira/browse/KAFKA-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903990#comment-15903990 ] Jun Rao commented on KAFKA-4433: [~mgharat], are you sure this is a real issue? reassigne

[jira] [Commented] (KAFKA-3143) inconsistent state in ZK when all replicas are dead

[ https://issues.apache.org/jira/browse/KAFKA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904086#comment-15904086 ] Jun Rao commented on KAFKA-3143: The ISR is only set to empty if unclean leader election i

[jira] [Commented] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904121#comment-15904121 ] Jun Rao commented on KAFKA-4790: [~pengwei], thanks for reporting that. That's a good find

[jira] [Commented] (KAFKA-4464) Clean shutdown of broker fails due to controller error

[ https://issues.apache.org/jira/browse/KAFKA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904151#comment-15904151 ] Jun Rao commented on KAFKA-4464: When the process hang, could you take a thread dump and s

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904215#comment-15904215 ] Jun Rao commented on KAFKA-4277: [~Wrikken], [~steven.aerts], according to Zookeeper's gua

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923516#comment-15923516 ] Jun Rao commented on KAFKA-4277: [~Wrikken], the only case when we need to re-register the

[jira] [Created] (KAFKA-4896) Offset loading can use more threads

Jun Rao created KAFKA-4896: -- Summary: Offset loading can use more threads Key: KAFKA-4896 URL: https://issues.apache.org/jira/browse/KAFKA-4896 Project: Kafka Issue Type: Improvement Compo

[jira] [Commented] (KAFKA-4896) Offset loading can use more threads

[ https://issues.apache.org/jira/browse/KAFKA-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924617#comment-15924617 ] Jun Rao commented on KAFKA-4896: One thing we could probably do is to just set the threads

[jira] [Commented] (KAFKA-4888) offset 449883 is invalid, cause: Record is corrupt (stored crc = 2171407101, computed crc = 1371274824)

[ https://issues.apache.org/jira/browse/KAFKA-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926322#comment-15926322 ] Jun Rao commented on KAFKA-4888: [~eduardo.s.neto] and [~chengc], is the issue persistent,

[jira] [Created] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

Jun Rao created KAFKA-4907: -- Summary: compacted topic shouldn't reject messages with old timestamp Key: KAFKA-4907 URL: https://issues.apache.org/jira/browse/KAFKA-4907 Project: Kafka Issue Type: B

[jira] [Commented] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927054#comment-15927054 ] Jun Rao commented on KAFKA-4907: [~becket_qin], could you confirm if this is a real issue?

[jira] [Commented] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

[ https://issues.apache.org/jira/browse/KAFKA-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927265#comment-15927265 ] Jun Rao commented on KAFKA-4907: [~becket_qin], I was referring to the following code in K

[jira] [Commented] (KAFKA-4888) offset 449883 is invalid, cause: Record is corrupt (stored crc = 2171407101, computed crc = 1371274824)

[ https://issues.apache.org/jira/browse/KAFKA-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927500#comment-15927500 ] Jun Rao commented on KAFKA-4888: [~HanlinLiu], thanks for the info. Were there any issue w

[jira] [Commented] (KAFKA-4901) Make ProduceRequest thread-safe

[ https://issues.apache.org/jira/browse/KAFKA-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928347#comment-15928347 ] Jun Rao commented on KAFKA-4901: Not sure why the PR didn't show up here. Merged https://

[jira] [Resolved] (KAFKA-4894) Fix findbugs "default character set in use" warnings

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

[jira] [Resolved] (KAFKA-4817) Implement idempotent producer

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

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset (KIP-101)

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957938#comment-15957938 ] Jun Rao commented on KAFKA-1211: The PR for this issue is https://github.com/apache/kafka/

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958124#comment-15958124 ] Jun Rao commented on KAFKA-5007: [~joseph.alias...@gmail.com], thanks for reporting this.

[jira] [Updated] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset (KIP-101)

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1211: --- Resolution: Fixed Status: Resolved (was: Patch Available) The PR has been merged. Thanks, [~benstopfo

[jira] [Created] (KAFKA-5035) throttling_test fails due to parsing exception in console consumer

Jun Rao created KAFKA-5035: -- Summary: throttling_test fails due to parsing exception in console consumer Key: KAFKA-5035 URL: https://issues.apache.org/jira/browse/KAFKA-5035 Project: Kafka Issue T

[jira] [Created] (KAFKA-5036) Followups from KIP-101

Jun Rao created KAFKA-5036: -- Summary: Followups from KIP-101 Key: KAFKA-5036 URL: https://issues.apache.org/jira/browse/KAFKA-5036 Project: Kafka Issue Type: Improvement Affects Versions: 0.11.0

[jira] [Commented] (KAFKA-5035) throttling_test fails due to parsing exception in console consumer

[ https://issues.apache.org/jira/browse/KAFKA-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959915#comment-15959915 ] Jun Rao commented on KAFKA-5035: It seems that one way to fix the issue is to use acks=all

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960879#comment-15960879 ] Jun Rao commented on KAFKA-3955: One reason that can cause offsets to go out of order in t

[jira] [Resolved] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3919. Resolution: Fixed Assignee: Ben Stopford Fix Version/s: 0.11.0.0 This is fixed by KAFKA-1211

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961194#comment-15961194 ] Jun Rao commented on KAFKA-5007: Hmm, ReplicaFetcherThread is changed to use the client se

[jira] [Commented] (KAFKA-5011) Replica fetchers may need to down-convert messages during a selective message format upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961626#comment-15961626 ] Jun Rao commented on KAFKA-5011: Yes, this seems to be an issue. However, for this to happ

[jira] [Commented] (KAFKA-5049) Chroot check should be done for each ZkUtils instance

[ https://issues.apache.org/jira/browse/KAFKA-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966978#comment-15966978 ] Jun Rao commented on KAFKA-5049: [~ijuma], yes, that does seem to be a problem, [~anukin]

[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=15967705#comment-15967705 ] Jun Rao commented on KAFKA-2729: Thanks for the additional info. In both [~Ronghua Lin] an

[jira] [Created] (KAFKA-5068) Optionally print out metrics after running the perf tests

Jun Rao created KAFKA-5068: -- Summary: Optionally print out metrics after running the perf tests Key: KAFKA-5068 URL: https://issues.apache.org/jira/browse/KAFKA-5068 Project: Kafka Issue Type: Impro

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968209#comment-15968209 ] Jun Rao commented on KAFKA-5062: One far fetched scenario is the following. A bad applicat

[jira] [Commented] (KAFKA-5068) Optionally print out metrics after running the perf tests

[ https://issues.apache.org/jira/browse/KAFKA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969076#comment-15969076 ] Jun Rao commented on KAFKA-5068: [~huxi_2b], I actually meant all the low level metrics th

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969167#comment-15969167 ] Jun Rao commented on KAFKA-5062: Currently, we decompress messages on the broker just to v

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971929#comment-15971929 ] Jun Rao commented on KAFKA-5007: [~joseph.alias...@gmail.com], the socket leak could be at

[jira] [Updated] (KAFKA-5069) add controller integration tests

[ https://issues.apache.org/jira/browse/KAFKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5069: --- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available) Issue res

[jira] [Resolved] (KAFKA-5068) Optionally print out metrics after running the perf tests

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

[jira] [Resolved] (KAFKA-451) follower replica may need to backoff the fetching if leader is not ready yet

[ https://issues.apache.org/jira/browse/KAFKA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-451. --- Resolution: Not A Problem [~jozi-k], thanks for your interest. As Ismael mentioned, this issue actually has al

[jira] [Commented] (KAFKA-566) Add last modified time to the TopicMetadataRequest

[ https://issues.apache.org/jira/browse/KAFKA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977395#comment-15977395 ] Jun Rao commented on KAFKA-566: --- [~jozi-k], thanks for your interest. I am not sure if [~srih

[jira] [Commented] (KAFKA-5100) ProducerPerformanceService failing due to parsing error

[ https://issues.apache.org/jira/browse/KAFKA-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978863#comment-15978863 ] Jun Rao commented on KAFKA-5100: It seems the issue is that we now print the total before

[jira] [Resolved] (KAFKA-5100) ProducerPerformanceService failing due to parsing error

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

[jira] [Created] (KAFKA-5109) validate the output of ProducerPerformance and ConsumerPerformance in integration test

Jun Rao created KAFKA-5109: -- Summary: validate the output of ProducerPerformance and ConsumerPerformance in integration test Key: KAFKA-5109 URL: https://issues.apache.org/jira/browse/KAFKA-5109 Project: Kaf

[jira] [Commented] (KAFKA-5100) ProducerPerformanceService failing due to parsing error

[ https://issues.apache.org/jira/browse/KAFKA-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979291#comment-15979291 ] Jun Rao commented on KAFKA-5100: Filed https://issues.apache.org/jira/browse/KAFKA-5109 so

[jira] [Updated] (KAFKA-5109) validate the output of ProducerPerformance and ConsumerPerformance in integration test

[ https://issues.apache.org/jira/browse/KAFKA-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5109: --- Description: Our system tests parse the output of ProducerPerformance and ConsumerPerformance. So, it would b

[jira] [Commented] (KAFKA-5100) ProducerPerformanceService failing due to parsing error

[ https://issues.apache.org/jira/browse/KAFKA-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980028#comment-15980028 ] Jun Rao commented on KAFKA-5100: It seems that tests/kafkatest/sanity_checks/test_performa

[jira] [Commented] (KAFKA-1841) OffsetCommitRequest API - timestamp field is not versioned

[ https://issues.apache.org/jira/browse/KAFKA-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274301#comment-14274301 ] Jun Rao commented on KAFKA-1841: Updated reviewboard https://reviews.apache.org/r/29692/di

[jira] [Updated] (KAFKA-1841) OffsetCommitRequest API - timestamp field is not versioned

[ https://issues.apache.org/jira/browse/KAFKA-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1841: --- Attachment: kafka-1841_2015-01-12_14:30:24.patch > OffsetCommitRequest API - timestamp field is not versioned

[jira] [Updated] (KAFKA-1723) make the metrics name in new producer more standard

[ https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1723: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch. +1. Committed to 0.8.

[jira] [Updated] (KAFKA-1841) OffsetCommitRequest API - timestamp field is not versioned

[ https://issues.apache.org/jira/browse/KAFKA-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1841: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the review. Committed to 0.8.2.

[jira] [Commented] (KAFKA-1634) Improve semantics of timestamp in OffsetCommitRequests and update documentation

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274801#comment-14274801 ] Jun Rao commented on KAFKA-1634: Committed KAFKA-1841 to 0.8.2. It would be easier to inco

[jira] [Resolved] (KAFKA-1628) [New Java Producer] Topic which contains "." does not correct corresponding metric name

[ https://issues.apache.org/jira/browse/KAFKA-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1628. Resolution: Duplicate > [New Java Producer] Topic which contains "." does not correct corresponding > metr

[jira] [Updated] (KAFKA-1785) Consumer offset checker should show the offset manager and offsets partition

[ https://issues.apache.org/jira/browse/KAFKA-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1785: --- Fix Version/s: (was: 0.8.2) 0.8.3 Moving this to 0.8.3. > Consumer offset checker shou

[jira] [Commented] (KAFKA-1723) make the metrics name in new producer more standard

[ https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275715#comment-14275715 ] Jun Rao commented on KAFKA-1723: This is not a problem for now since all client provided t

[jira] [Commented] (KAFKA-1723) make the metrics name in new producer more standard

[ https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277582#comment-14277582 ] Jun Rao commented on KAFKA-1723: [~omkreddy], thanks for the delta patch. Since this is no

[jira] [Created] (KAFKA-1867) liveBroker list not updated on a cluster with no topics

Jun Rao created KAFKA-1867: -- Summary: liveBroker list not updated on a cluster with no topics Key: KAFKA-1867 URL: https://issues.apache.org/jira/browse/KAFKA-1867 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-1864) Revisit defaults for the internal offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-1864: -- Assignee: Jun Rao > Revisit defaults for the internal offsets topic > -

[jira] [Updated] (KAFKA-1864) Revisit defaults for the internal offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1864: --- Status: Patch Available (was: Open) > Revisit defaults for the internal offsets topic > -

[jira] [Updated] (KAFKA-1864) Revisit defaults for the internal offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1864: --- Attachment: kafka-1864.patch > Revisit defaults for the internal offsets topic > -

[jira] [Commented] (KAFKA-1864) Revisit defaults for the internal offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279616#comment-14279616 ] Jun Rao commented on KAFKA-1864: Attached is a patch. A couple of the unit tests fail beca

[jira] [Commented] (KAFKA-1864) Revisit defaults for the internal offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279615#comment-14279615 ] Jun Rao commented on KAFKA-1864: Created reviewboard https://reviews.apache.org/r/29952/di

[jira] [Created] (KAFKA-1868) ConsoleConsumer shouldn't override dual.commit.enabled to false if not explicitly set

Jun Rao created KAFKA-1868: -- Summary: ConsoleConsumer shouldn't override dual.commit.enabled to false if not explicitly set Key: KAFKA-1868 URL: https://issues.apache.org/jira/browse/KAFKA-1868 Project: Kafk

[jira] [Updated] (KAFKA-1868) ConsoleConsumer shouldn't override dual.commit.enabled to false if not explicitly set

[ https://issues.apache.org/jira/browse/KAFKA-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1868: --- Status: Patch Available (was: Open) > ConsoleConsumer shouldn't override dual.commit.enabled to false if not

[jira] [Updated] (KAFKA-1868) ConsoleConsumer shouldn't override dual.commit.enabled to false if not explicitly set

[ https://issues.apache.org/jira/browse/KAFKA-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1868: --- Attachment: kafka-1868.patch > ConsoleConsumer shouldn't override dual.commit.enabled to false if not > expli

[jira] [Commented] (KAFKA-1868) ConsoleConsumer shouldn't override dual.commit.enabled to false if not explicitly set

[ https://issues.apache.org/jira/browse/KAFKA-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279626#comment-14279626 ] Jun Rao commented on KAFKA-1868: Created reviewboard https://reviews.apache.org/r/29953/di

[jira] [Commented] (KAFKA-1864) Revisit defaults for the internal offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279677#comment-14279677 ] Jun Rao commented on KAFKA-1864: Also, another impact in this patch is that the offset top

[jira] [Updated] (KAFKA-1868) ConsoleConsumer shouldn't override dual.commit.enabled to false if not explicitly set

[ https://issues.apache.org/jira/browse/KAFKA-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1868: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the review. Committed to both 0.

[jira] [Commented] (KAFKA-1871) Kafka Producer constructor hungs in case of wrong 'serializer.class' property

[ https://issues.apache.org/jira/browse/KAFKA-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280677#comment-14280677 ] Jun Rao commented on KAFKA-1871: Could you get the stack trace? Thanks, > Kafka Producer

[jira] [Commented] (KAFKA-1649) Protocol documentation does not indicate that ReplicaNotAvailable can be ignored

[ https://issues.apache.org/jira/browse/KAFKA-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280724#comment-14280724 ] Jun Rao commented on KAFKA-1649: This is discussed in the mailing list. The behavior alrea

[jira] [Commented] (KAFKA-1870) Cannot commit with simpleConsumer on Zookeeper only with Java API

[ https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280728#comment-14280728 ] Jun Rao commented on KAFKA-1870: Created reviewboard https://reviews.apache.org/r/29977/di

[jira] [Updated] (KAFKA-1870) Cannot commit with simpleConsumer on Zookeeper only with Java API

[ https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1870: --- Attachment: kafka-1870.patch > Cannot commit with simpleConsumer on Zookeeper only with Java API > ---

[jira] [Updated] (KAFKA-1870) Cannot commit with simpleConsumer on Zookeeper only with Java API

[ https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1870: --- Assignee: Jun Rao Status: Patch Available (was: Open) > Cannot commit with simpleConsumer on Zookeeper

<    1   2   3   4   5   6   7   8   9   10   >