[jira] [Updated] (KAFKA-4506) Refactor AbstractRequest to contain version information

[ https://issues.apache.org/jira/browse/KAFKA-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4506: --- Fix Version/s: 0.10.2.0 > Refactor AbstractRequest to contain version information >

[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

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

[jira] [Updated] (KAFKA-4734) timeindex on old segments not trimmed to actual size

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

[jira] [Resolved] (KAFKA-4727) A Production server configuration needs to be updated

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

[jira] [Resolved] (KAFKA-4441) Kafka Monitoring is incorrect during rapid topic creation and deletion

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

[jira] [Commented] (KAFKA-4734) timeindex on old segments not trimmed to actual size

[ https://issues.apache.org/jira/browse/KAFKA-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852317#comment-15852317 ] Jun Rao commented on KAFKA-4734: [~becket_qin], do you think you could take a look at this? Thanks. >

[jira] [Created] (KAFKA-4734) timeindex on old segments not trimmed to actual size

Jun Rao created KAFKA-4734: -- Summary: timeindex on old segments not trimmed to actual size Key: KAFKA-4734 URL: https://issues.apache.org/jira/browse/KAFKA-4734 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851904#comment-15851904 ] Jun Rao commented on KAFKA-4614: [~thetaphi], thanks for the info. Much appreciated! > Long GC pause

[jira] [Created] (KAFKA-4727) A Production server configuration needs to be updated

Jun Rao created KAFKA-4727: -- Summary: A Production server configuration needs to be updated Key: KAFKA-4727 URL: https://issues.apache.org/jira/browse/KAFKA-4727 Project: Kafka Issue Type:

[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=15843636#comment-15843636 ] Jun Rao commented on KAFKA-4277: According to the following, it doesn't seem this can happen in ZK.

[jira] [Updated] (KAFKA-4229) Controller can't start after several zk expired event

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

[jira] [Updated] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3450: --- Assignee: (was: Jun Rao) > Producer blocks on send to topic that doesn't exist if auto create is disabled

[jira] [Updated] (KAFKA-4432) ProducerPerformance.java : Add support to supply custom message payloads.

[ https://issues.apache.org/jira/browse/KAFKA-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4432: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2158

[jira] [Updated] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4614: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2352

[jira] [Resolved] (KAFKA-4589) Add documentation for SASL/SCRAM

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

[jira] [Updated] (KAFKA-3857) Additional log cleaner metrics

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

[jira] [Updated] (KAFKA-3751) Add support for SASL/SCRAM mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3751: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2086

[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=15803184#comment-15803184 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], I did the following test. (1) Run Kafka 0.10.1.1

[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=15802131#comment-15802131 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], thanks for the update. Did you get the 0.10.1.1

[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=15801977#comment-15801977 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], similar to [~becket_qin], I couldn't reproduce

[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=15799565#comment-15799565 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], if you could attach the problematic .log file to

[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=15799192#comment-15799192 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], sorry for the production issue this is causing.

[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=15798702#comment-15798702 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], thanks for reporting this. It would be good to

[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=15768759#comment-15768759 ] Jun Rao commented on KAFKA-4277: [~fpj], in KAFKA-1387, you had the following comment: "If a client has

[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] >

[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

[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] [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=15752252#comment-15752252 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], the deadlock seems to be the same as in

[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

[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=15750154#comment-15750154 ] Jun Rao commented on KAFKA-4545: One potential way to fix this is when cleaning a segment after the dirty

[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

[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=15748966#comment-15748966 ] Jun Rao commented on KAFKA-4529: Committed [~becket_qin]'s patch to 0.10.1 branch. Leaving the jira open

[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=15746393#comment-15746393 ] Jun Rao commented on KAFKA-4477: [~tdevoe], from the controller log, starting from 19:59:13, the

[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=15745817#comment-15745817 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], [~tdevoe], was the following exception in the

[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=15745813#comment-15745813 ] Jun Rao commented on KAFKA-4477: [~tdevoe], thanks for the clarification. Then, it looks similar to what'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=15745782#comment-15745782 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], the 0.10.1.1 release will need RC1 since we need

[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

[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=15743987#comment-15743987 ] Jun Rao commented on KAFKA-4529: [~becket_qin], do you think you have time to fix this issue? The easiest

[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

[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=15743756#comment-15743756 ] Jun Rao commented on KAFKA-4497: Got it. I thought Robert was showing the DumpLogSegment output and I was

[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=15743748#comment-15743748 ] Jun Rao commented on KAFKA-4477: [~michael.andre.pearce], the issue that you reported is a bit weird, but

[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=15743728#comment-15743728 ] Jun Rao commented on KAFKA-4477: [~tdevoe], thanks for sharing the log. On node 1001 and 1003, the

[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=15743297#comment-15743297 ] Jun Rao commented on KAFKA-4497: [~becket_qin], it could be. Where do we lose the negative sign bit? >

[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=15742677#comment-15742677 ] Jun Rao commented on KAFKA-4497: [~becket_qin], thanks for providing the fix. The fix seems to address the

[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=15724000#comment-15724000 ] Jun Rao commented on KAFKA-4454: [~mgharat], I understand the problem that you described. However, I am

[jira] [Commented] (KAFKA-4443) Controller should send UpdateMetadataRequest prior to LeaderAndIsrRequest during failover

[ https://issues.apache.org/jira/browse/KAFKA-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705851#comment-15705851 ] Jun Rao commented on KAFKA-4443: [~lindong], thanks for filing the jira. A couple of questions. (1) I am

[jira] [Resolved] (KAFKA-1429) Yet another deadlock in controller shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1429. Resolution: Duplicate Assignee: (was: Neha Narkhede) This is already fixed by KAFKA-4360. > Yet

[jira] [Commented] (KAFKA-4021) system tests need to enable trace level logging for controller and state-change log

[ https://issues.apache.org/jira/browse/KAFKA-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688546#comment-15688546 ] Jun Rao commented on KAFKA-4021: [~ewencp], those trace level logging only happens when there are broker

[jira] [Comment Edited] (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=15325496#comment-15325496 ] Jun Rao edited comment on KAFKA-1120 at 11/23/16 1:03 AM: -- A better way is

[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=15688448#comment-15688448 ] Jun Rao commented on KAFKA-1120: [~wushujames], it seems that the controller did detect that broker came

[jira] [Resolved] (KAFKA-2089) MetadataTest transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2089. Resolution: Fixed Fix Version/s: (was: 0.9.0.0) 0.10.2.0 Issue resolved by

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603377#comment-15603377 ] Jun Rao commented on KAFKA-4099: [~becket_qin], thanks the explanation. What you described makes sense. So

[jira] [Created] (KAFKA-4332) kafka.api.UserQuotaTest.testThrottledProducerConsumer transient unit test failure

Jun Rao created KAFKA-4332: -- Summary: kafka.api.UserQuotaTest.testThrottledProducerConsumer transient unit test failure Key: KAFKA-4332 URL: https://issues.apache.org/jira/browse/KAFKA-4332 Project: Kafka

[jira] [Reopened] (KAFKA-2089) MetadataTest transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reopened KAFKA-2089: Reopening this issue. Saw the following transient failure in trunk. org.apache.kafka.clients.MetadataTest >

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15596037#comment-15596037 ] Jun Rao commented on KAFKA-4099: I had two use cases of time-based rolling in mind. The first one is for

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15594095#comment-15594095 ] Jun Rao commented on KAFKA-4099: [~becket_qin], Ewen brought up another example that may still lead to

[jira] [Commented] (KAFKA-4313) ISRs may thrash when replication quota is enabled

[ https://issues.apache.org/jira/browse/KAFKA-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587386#comment-15587386 ] Jun Rao commented on KAFKA-4313: One way to fix this is that we avoid throttling those replicas in the

[jira] [Created] (KAFKA-4313) ISRs may thrash when replication quota is enabled

Jun Rao created KAFKA-4313: -- Summary: ISRs may thrash when replication quota is enabled Key: KAFKA-4313 URL: https://issues.apache.org/jira/browse/KAFKA-4313 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-4287) auto generate DynamicConfig in docs

Jun Rao created KAFKA-4287: -- Summary: auto generate DynamicConfig in docs Key: KAFKA-4287 URL: https://issues.apache.org/jira/browse/KAFKA-4287 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-4286) metric reporter may hit NullPointerException during shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562886#comment-15562886 ] Jun Rao commented on KAFKA-4286: There are a few ways that we could fix this. One way is to obtain the

[jira] [Created] (KAFKA-4286) metric reporter may hit NullPointerException during shutdown

Jun Rao created KAFKA-4286: -- Summary: metric reporter may hit NullPointerException during shutdown Key: KAFKA-4286 URL: https://issues.apache.org/jira/browse/KAFKA-4286 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556670#comment-15556670 ] Jun Rao commented on KAFKA-3410: [~james cheng], the proposal in KAFKA-1211 should prevent the halting

[jira] [Commented] (KAFKA-4274) KafkaConsumer.offsetsForTimes() hangs and times out on an empty map

[ https://issues.apache.org/jira/browse/KAFKA-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556217#comment-15556217 ] Jun Rao commented on KAFKA-4274: [~becket_qin], do you want to fix this? Thanks. >

[jira] [Created] (KAFKA-4274) KafkaConsumer.offsetsForTimes() hangs and times out on an empty map

Jun Rao created KAFKA-4274: -- Summary: KafkaConsumer.offsetsForTimes() hangs and times out on an empty map Key: KAFKA-4274 URL: https://issues.apache.org/jira/browse/KAFKA-4274 Project: Kafka Issue

[jira] [Resolved] (KAFKA-4214) kafka-reassign-partitions fails all the time when brokers are bounced during reassignment

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

[jira] [Commented] (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:comment-tabpanel=15524480#comment-15524480 ] Jun Rao commented on KAFKA-3919: [~BigAndy], the error trace in the description of the jira only happens

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

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1211: --- Assignee: (was: Guozhang Wang) > Hold the produce request with ack > 1 in purgatory until replicas' HW

[jira] [Commented] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524361#comment-15524361 ] Jun Rao commented on KAFKA-1342: A similar incident was reported in

[jira] [Updated] (KAFKA-4055) Add system tests for secure quotas

[ https://issues.apache.org/jira/browse/KAFKA-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4055: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1860

[jira] [Commented] (KAFKA-4207) Partitions stopped after a rapid restart of a broker

[ https://issues.apache.org/jira/browse/KAFKA-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517526#comment-15517526 ] Jun Rao commented on KAFKA-4207: This seems to be the same issue as reported in

[jira] [Commented] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514723#comment-15514723 ] Jun Rao commented on KAFKA-4178: [~benstopford], thanks for the patch. I like your idea of consolidating

[jira] [Commented] (KAFKA-4178) Replication Throttling: Consolidate Rate Classes

[ https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508193#comment-15508193 ] Jun Rao commented on KAFKA-4178: [~jjkoshy], [~aauradkar], could you provide some context on the changes

[jira] [Created] (KAFKA-4195) support throttling on request rate

Jun Rao created KAFKA-4195: -- Summary: support throttling on request rate Key: KAFKA-4195 URL: https://issues.apache.org/jira/browse/KAFKA-4195 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-4195) support throttling on request rate

[ https://issues.apache.org/jira/browse/KAFKA-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505615#comment-15505615 ] Jun Rao commented on KAFKA-4195: We will need to do a KIP on the design first. > support throttling on

[jira] [Updated] (KAFKA-4079) Document quota configuration changes from KIP-55

[ https://issues.apache.org/jira/browse/KAFKA-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4079: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1847

[jira] [Updated] (KAFKA-3492) support quota based on authenticated user name

[ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3492: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1753

[jira] [Updated] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1464: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1776

[jira] [Commented] (KAFKA-3964) Metadata update requests are sometimes received after LeaderAndIsrRequests

[ https://issues.apache.org/jira/browse/KAFKA-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493523#comment-15493523 ] Jun Rao commented on KAFKA-3964: [~krishna97], it seems that this is the same issue as in

[jira] [Resolved] (KAFKA-1981) Make log compaction point configurable

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

[jira] [Commented] (KAFKA-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469233#comment-15469233 ] Jun Rao commented on KAFKA-4074: [~jjkoshy], is this the same issue as

[jira] [Updated] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4099: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1809

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450713#comment-15450713 ] Jun Rao commented on KAFKA-3144: Related to this. It will also be useful to optionally show the consumer

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to base on the file create time instead of timestamp of the first message.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450309#comment-15450309 ] Jun Rao commented on KAFKA-4099: [~becket_qin], thanks for the proposal. Your suggestion sounds reasonable

[jira] [Commented] (KAFKA-4088) Add regression check for KAFKA-4073

[ https://issues.apache.org/jira/browse/KAFKA-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437963#comment-15437963 ] Jun Rao commented on KAFKA-4088: It may be possible to cover this in a unit test.

[jira] [Resolved] (KAFKA-4015) Change cleanup.policy config to accept a list of valid policies

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

[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=15435073#comment-15435073 ] Jun Rao commented on KAFKA-4084: [~tcrayford-heroku], if you check

[jira] [Commented] (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:comment-tabpanel=15433768#comment-15433768 ] Jun Rao commented on KAFKA-3083: Someone encountered another issue related to this. After a broker's ZK

[jira] [Resolved] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

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

[jira] [Commented] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

[ https://issues.apache.org/jira/browse/KAFKA-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431460#comment-15431460 ] Jun Rao commented on KAFKA-4073: One way to fix that is to check if the timestamp is present in the source

[jira] [Created] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

Jun Rao created KAFKA-4073: -- Summary: MirrorMaker should handle mirroring messages w/o timestamp better Key: KAFKA-4073 URL: https://issues.apache.org/jira/browse/KAFKA-4073 Project: Kafka Issue

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3894: --- Assignee: Tom Crayford [~tcrayford-heroku], thanks for the patch. Filed a followup jira KAFKA-4072 to

[jira] [Created] (KAFKA-4072) improving memory usage in LogCleaner

Jun Rao created KAFKA-4072: -- Summary: improving memory usage in LogCleaner Key: KAFKA-4072 URL: https://issues.apache.org/jira/browse/KAFKA-4072 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

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

[jira] [Created] (KAFKA-4067) improve the handling of IOException in log.close()

Jun Rao created KAFKA-4067: -- Summary: improve the handling of IOException in log.close() Key: KAFKA-4067 URL: https://issues.apache.org/jira/browse/KAFKA-4067 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3163: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1215

[jira] [Resolved] (KAFKA-4044) log actual socket send/receive buffer size after connecting in Selector

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

[jira] [Commented] (KAFKA-4050) Allow configuration of the PRNG used for SSL

[ https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423368#comment-15423368 ] Jun Rao commented on KAFKA-4050: [~toddpalino], thanks for reporting this. Do you know how often PRNG is

[jira] [Created] (KAFKA-4044) log actual socket send/receive buffer size after connecting in Selector

Jun Rao created KAFKA-4044: -- Summary: log actual socket send/receive buffer size after connecting in Selector Key: KAFKA-4044 URL: https://issues.apache.org/jira/browse/KAFKA-4044 Project: Kafka

[jira] [Updated] (KAFKA-2946) DeleteTopic - protocol and server side implementation

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

[jira] [Created] (KAFKA-4035) AclCommand should allow Describe operation on groups

Jun Rao created KAFKA-4035: -- Summary: AclCommand should allow Describe operation on groups Key: KAFKA-4035 URL: https://issues.apache.org/jira/browse/KAFKA-4035 Project: Kafka Issue Type: Bug

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