[jira] [Commented] (KAFKA-1983) TestEndToEndLatency can be unreliable after hard kill

[ https://issues.apache.org/jira/browse/KAFKA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334096#comment-14334096 ] Jun Rao commented on KAFKA-1983: An easy solution is probably to avoid committing offset a

[jira] [Commented] (KAFKA-1724) Errors after reboot in single node setup

[ https://issues.apache.org/jira/browse/KAFKA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334130#comment-14334130 ] Jun Rao commented on KAFKA-1724: [~sriharsha], so, this is fixed as part of KAFKA-1760? >

[jira] [Created] (KAFKA-1984) java producer may miss an available partition

Jun Rao created KAFKA-1984: -- Summary: java producer may miss an available partition Key: KAFKA-1984 URL: https://issues.apache.org/jira/browse/KAFKA-1984 Project: Kafka Issue Type: Bug Affects V

[jira] [Updated] (KAFKA-1984) java producer may miss an available partition

[ https://issues.apache.org/jira/browse/KAFKA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1984: --- Status: Patch Available (was: Open) > java producer may miss an available partition > ---

[jira] [Commented] (KAFKA-1984) java producer may miss an available partition

[ https://issues.apache.org/jira/browse/KAFKA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335142#comment-14335142 ] Jun Rao commented on KAFKA-1984: There are actual two problems. 1. The way that we select

[jira] [Updated] (KAFKA-1984) java producer may miss an available partition

[ https://issues.apache.org/jira/browse/KAFKA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1984: --- Attachment: kafka-1984.patch > java producer may miss an available partition > ---

[jira] [Commented] (KAFKA-1984) java producer may miss an available partition

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

[jira] [Updated] (KAFKA-1984) java producer may miss an available partition

[ https://issues.apache.org/jira/browse/KAFKA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1984: --- Attachment: kafka-1984.patch > java producer may miss an available partition > ---

[jira] [Commented] (KAFKA-1984) java producer may miss an available partition

[ https://issues.apache.org/jira/browse/KAFKA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335184#comment-14335184 ] Jun Rao commented on KAFKA-1984: Attaching a fix for 0.8.2 too. > java producer may miss

[jira] [Commented] (KAFKA-1984) java producer may miss an available partition

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

[jira] [Updated] (KAFKA-1984) java producer may miss an available partition

[ https://issues.apache.org/jira/browse/KAFKA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1984: --- Priority: Blocker (was: Major) Fix Version/s: 0.8.2.1 Marking this a blocker for 0.8.2.1 since it af

[jira] [Updated] (KAFKA-1984) java producer may miss an available partition

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

[jira] [Updated] (KAFKA-1724) Errors after reboot in single node setup

[ https://issues.apache.org/jira/browse/KAFKA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1724: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Errors after reboot in single node setup

[jira] [Commented] (KAFKA-1865) Add a flush() call to the new producer API

[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338944#comment-14338944 ] Jun Rao commented on KAFKA-1865: The KIP (https://cwiki.apache.org/confluence/display/KAF

[jira] [Updated] (KAFKA-1881) transient unit test failure in testDeleteTopicWithCleaner due to OOME

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

[jira] [Updated] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1400: --- Attachment: kafka-1400.patch > transient unit test failure in SocketServerTest > -

[jira] [Updated] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1400: --- Assignee: Jun Rao (was: Neha Narkhede) Status: Patch Available (was: Reopened) > transient unit test f

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

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

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339452#comment-14339452 ] Jun Rao commented on KAFKA-1400: Provide a simple fix to send enough bytes to trigger a so

[jira] [Commented] (KAFKA-1988) org.apache.kafka.common.utils.Utils.abs method returns wrong value for negative numbers.

[ https://issues.apache.org/jira/browse/KAFKA-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339500#comment-14339500 ] Jun Rao commented on KAFKA-1988: Thanks for the patch. +1. We actually made the same mist

[jira] [Updated] (KAFKA-1988) org.apache.kafka.common.utils.Utils.abs method returns wrong value for negative numbers.

[ https://issues.apache.org/jira/browse/KAFKA-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1988: --- Priority: Blocker (was: Major) Affects Version/s: 0.8.2.0 Fix Version/s: 0.8.2.1 Since t

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339552#comment-14339552 ] Jun Rao commented on KAFKA-1400: Well, this test is supposed to test the client behavior.

[jira] [Commented] (KAFKA-1988) org.apache.kafka.common.utils.Utils.abs method returns wrong value for negative numbers.

[ https://issues.apache.org/jira/browse/KAFKA-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339751#comment-14339751 ] Jun Rao commented on KAFKA-1988: Actually, we can probably keep the same logic in determin

[jira] [Commented] (KAFKA-1988) org.apache.kafka.common.utils.Utils.abs method returns wrong value for negative numbers.

[ https://issues.apache.org/jira/browse/KAFKA-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340663#comment-14340663 ] Jun Rao commented on KAFKA-1988: Hi, Tong, My suggestion is slightly different. My point

[jira] [Commented] (KAFKA-1400) transient unit test failure in SocketServerTest

[ https://issues.apache.org/jira/browse/KAFKA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340701#comment-14340701 ] Jun Rao commented on KAFKA-1400: Yes, that's probably the goal of this test. The checking

[jira] [Updated] (KAFKA-1400) transient unit test failure in SocketServerTest

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

[jira] [Commented] (KAFKA-1664) Kafka does not properly parse multiple ZK nodes with non-root chroot

[ https://issues.apache.org/jira/browse/KAFKA-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341660#comment-14341660 ] Jun Rao commented on KAFKA-1664: Thanks for the patch. The patch makes every create operat

[jira] [Resolved] (KAFKA-952) a broker should unregister certain ZK watchers afte it is no longer the controller

[ https://issues.apache.org/jira/browse/KAFKA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-952. --- Resolution: Duplicate This is already fixed in KAFKA-1578. > a broker should unregister certain ZK watchers af

[jira] [Commented] (KAFKA-1994) Evaluate performance effect of chroot check on Topic creation

[ https://issues.apache.org/jira/browse/KAFKA-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344572#comment-14344572 ] Jun Rao commented on KAFKA-1994: Ashish, The code path for creating a topic may not be op

[jira] [Created] (KAFKA-2001) OffsetCommitTest hang during setup

Jun Rao created KAFKA-2001: -- Summary: OffsetCommitTest hang during setup Key: KAFKA-2001 URL: https://issues.apache.org/jira/browse/KAFKA-2001 Project: Kafka Issue Type: Bug Components: co

[jira] [Updated] (KAFKA-1999) Fix failing unit-test: kafka.api.ProducerFailureHandlingTest > testNotEnoughReplicasAfterBrokerShutdown

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

[jira] [Resolved] (KAFKA-1976) transient unit test failure in ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown

[ https://issues.apache.org/jira/browse/KAFKA-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1976. Resolution: Duplicate Duplicate of KAFKA-1999. > transient unit test failure in > ProducerFailureHandlingT

[jira] [Commented] (KAFKA-1809) Refactor brokers to allow listening on multiple ports and IPs

[ https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347236#comment-14347236 ] Jun Rao commented on KAFKA-1809: Thanks for the patch. Some comments. 1. KafkaConfig: 1.1

[jira] [Created] (KAFKA-2010) unit tests sometimes are slow during shutdown

Jun Rao created KAFKA-2010: -- Summary: unit tests sometimes are slow during shutdown Key: KAFKA-2010 URL: https://issues.apache.org/jira/browse/KAFKA-2010 Project: Kafka Issue Type: Bug R

[jira] [Commented] (KAFKA-2010) unit tests sometimes are slow during shutdown

[ https://issues.apache.org/jira/browse/KAFKA-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352321#comment-14352321 ] Jun Rao commented on KAFKA-2010: The long delay always happens during the shutdown of a mu

[jira] [Commented] (KAFKA-2010) unit tests sometimes are slow during shutdown

[ https://issues.apache.org/jira/browse/KAFKA-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353190#comment-14353190 ] Jun Rao commented on KAFKA-2010: [~gwenshap], thanks for the info. Steve Miller also point

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354068#comment-14354068 ] Jun Rao commented on KAFKA-1461: [~sriharsha], thanks for the patch. Managing the backoff

[jira] [Commented] (KAFKA-2010) unit tests sometimes are slow during shutdown

[ https://issues.apache.org/jira/browse/KAFKA-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354072#comment-14354072 ] Jun Rao commented on KAFKA-2010: [~guozhang], this seems to happen frequently to me on Mac

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354081#comment-14354081 ] Jun Rao commented on KAFKA-1461: [~sriharsha], since this affects the unit test performanc

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354272#comment-14354272 ] Jun Rao commented on KAFKA-1461: [~sriharsha], thanks. Your understanding is correct. We c

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355301#comment-14355301 ] Jun Rao commented on KAFKA-1461: [~guozhang], my concern is on the implementation of the D

[jira] [Commented] (KAFKA-1910) Refactor KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355640#comment-14355640 ] Jun Rao commented on KAFKA-1910: The most recent jenkins run has the following two unit te

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357668#comment-14357668 ] Jun Rao commented on KAFKA-1461: [~sriharsha] and [~guozhang], thinking about this a bit m

[jira] [Commented] (KAFKA-1910) Refactor KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357725#comment-14357725 ] Jun Rao commented on KAFKA-1910: Are the changes in ConsumerTest needed? The extra logging

[jira] [Commented] (KAFKA-1910) Refactor KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357145#comment-14357145 ] Jun Rao commented on KAFKA-1910: [~guozhang], I still see the following transient unit tes

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359316#comment-14359316 ] Jun Rao commented on KAFKA-1461: [~charmalloc], I don't think we need a KIP for this eithe

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359368#comment-14359368 ] Jun Rao commented on KAFKA-1461: Hmm, I don't think we removed or changed any config. Whic

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359394#comment-14359394 ] Jun Rao commented on KAFKA-1461: [~sriharsha], thanks for the patch. +1 on RB 31927 after

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359402#comment-14359402 ] Jun Rao commented on KAFKA-1461: [~sriharsha], for the changes in RB 31366. We need to thi

[jira] [Resolved] (KAFKA-2010) unit tests sometimes are slow during shutdown

[ https://issues.apache.org/jira/browse/KAFKA-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2010. Resolution: Duplicate This is fixed in KAFKA-1461. The unit tests time went down from 12 mins to 8.5 mins o

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359427#comment-14359427 ] Jun Rao commented on KAFKA-1461: Also, in AbstractFetcherThread, we probably should use th

[jira] [Commented] (KAFKA-902) Randomize backoff on the clients for metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359497#comment-14359497 ] Jun Rao commented on KAFKA-902: --- Thanks for the patch. A few comments. 1. I feel that it's s

[jira] [Commented] (KAFKA-1910) Refactor KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359506#comment-14359506 ] Jun Rao commented on KAFKA-1910: In BounceBrokerScheduler, is there a particular reason th

[jira] [Created] (KAFKA-2016) RollingBounceTest takes long

Jun Rao created KAFKA-2016: -- Summary: RollingBounceTest takes long Key: KAFKA-2016 URL: https://issues.apache.org/jira/browse/KAFKA-2016 Project: Kafka Issue Type: Improvement Reporter:

[jira] [Commented] (KAFKA-2016) RollingBounceTest takes long

[ https://issues.apache.org/jira/browse/KAFKA-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359556#comment-14359556 ] Jun Rao commented on KAFKA-2016: Perhaps we can first figure out where the time is spent a

[jira] [Commented] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360637#comment-14360637 ] Jun Rao commented on KAFKA-1927: The following is a rough outline to do this. 1. kafka.ne

[jira] [Commented] (KAFKA-1684) Implement TLS/SSL authentication

[ https://issues.apache.org/jira/browse/KAFKA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361470#comment-14361470 ] Jun Rao commented on KAFKA-1684: [~sriharsha], just a high level comment. We have another

[jira] [Commented] (KAFKA-1926) Replace kafka.utils.Utils with o.a.k.common.utils.Utils

[ https://issues.apache.org/jira/browse/KAFKA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362111#comment-14362111 ] Jun Rao commented on KAFKA-1926: [~tongli], thanks the for patch. I made a pass of all met

[jira] [Commented] (KAFKA-1682) Security for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362638#comment-14362638 ] Jun Rao commented on KAFKA-1682: Just so that everyone knows the sequencing and who is wor

[jira] [Commented] (KAFKA-2020) I expect ReplicaNotAvailableException to have proper Javadocs

[ https://issues.apache.org/jira/browse/KAFKA-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363678#comment-14363678 ] Jun Rao commented on KAFKA-2020: The following is the protocol for TopicMetadataResponse.

[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=14367394#comment-14367394 ] Jun Rao commented on KAFKA-1634: [~guozhang], [~jjkoshy], in order to work on KAFKA-1927,

[jira] [Commented] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367396#comment-14367396 ] Jun Rao commented on KAFKA-1927: In order to work on this jira, we will need to merge KAFK

[jira] [Comment Edited] (KAFKA-1927) Replace requests in kafka.api with requests in org.apache.kafka.common.requests

[ https://issues.apache.org/jira/browse/KAFKA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367396#comment-14367396 ] Jun Rao edited comment on KAFKA-1927 at 3/18/15 4:18 PM: - In order

[jira] [Commented] (KAFKA-1930) Move server over to new metrics library

[ https://issues.apache.org/jira/browse/KAFKA-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369623#comment-14369623 ] Jun Rao commented on KAFKA-1930: Another thing that we need to think through is the histog

[jira] [Commented] (KAFKA-1688) Add authorization interface and naive implementation

[ https://issues.apache.org/jira/browse/KAFKA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371544#comment-14371544 ] Jun Rao commented on KAFKA-1688: [~lparth], having a TopicConfigCache to cache all topic c

[jira] [Resolved] (KAFKA-2037) Can't leave comments in Confluence

[ https://issues.apache.org/jira/browse/KAFKA-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-2037. Resolution: Fixed Just granted you the permission to Kafka wiki. > Can't leave comments in Confluence > ---

[jira] [Commented] (KAFKA-2042) New producer metadata update always get all topics.

[ https://issues.apache.org/jira/browse/KAFKA-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378954#comment-14378954 ] Jun Rao commented on KAFKA-2042: Could you explain a bit more when the new producer will s

[jira] [Commented] (KAFKA-2042) New producer metadata update always get all topics.

[ https://issues.apache.org/jira/browse/KAFKA-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379015#comment-14379015 ] Jun Rao commented on KAFKA-2042: If I start a console-producer w/o typing in any message,

[jira] [Commented] (KAFKA-527) Compression support does numerous byte copies

[ https://issues.apache.org/jira/browse/KAFKA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380657#comment-14380657 ] Jun Rao commented on KAFKA-527: --- [~ymatsuda], thanks for the patch. +1 and committed to trunk

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

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

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

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

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

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

[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 [https:

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

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

[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 [https:

[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 [https:

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

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

[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: Improveme

[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&focusedCommentId=15851904#comment-15851904 ] Jun Rao commented on KAFKA-4614: [~thetaphi], thanks for the info. Much appreciated! > Lo

[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&focusedCommentId=15852317#comment-15852317 ] Jun Rao commented on KAFKA-4734: [~becket_qin], do you think you could take a look at this

[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: Improveme

[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 [https://github.com/apa

[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 [https://github.com/apa

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

[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 Available)

[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-4462) Improved Kafka Client Compatibility Policy

[ https://issues.apache.org/jira/browse/KAFKA-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-4462: --- Fix Version/s: 0.10.2.0 > Improved Kafka Client Compatibility Policy > ---

[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&focusedCommentId=15858410#comment-15858410 ] Jun Rao commented on KAFKA-4195: Ismael brought up a good point that it may not be easy to

[jira] [Resolved] (KAFKA-4756) The auto-generated broker id should be passed to MetricReporter.configure

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

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868433#comment-15868433 ] Jun Rao commented on KAFKA-4340: [~becket_qin], after committing the patch in this jira. O

[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=15879700#comment-15879700 ] Jun Rao commented on KAFKA-2729: Sorry to hear about the impact to production. Grant menti

[jira] [Commented] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191094#comment-15191094 ] Jun Rao commented on KAFKA-3215: [~fpj], thanks for the analysis. Yes, it does seems that

[jira] [Resolved] (KAFKA-3215) controller may not be started when there are multiple ZK session expirations

[ https://issues.apache.org/jira/browse/KAFKA-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3215. Resolution: Fixed Fix Version/s: 0.9.0.0 > controller may not be started when there are multiple ZK s

[jira] [Resolved] (KAFKA-1215) Rack-Aware replica assignment option

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

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