[jira] [Commented] (KAFKA-3852) Clarify how to handle message format upgrade without killing performance

[ https://issues.apache.org/jira/browse/KAFKA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395092#comment-15395092 ] Ewen Cheslack-Postava commented on KAFKA-3852: -- I just grabbed it to try to get to it

[jira] [Commented] (KAFKA-3851) Add references to important installation/upgrade notes to release notes

[ https://issues.apache.org/jira/browse/KAFKA-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395078#comment-15395078 ] ASF GitHub Bot commented on KAFKA-3851: --- GitHub user ewencp opened a pull request:

[GitHub] kafka pull request #1670: KAFKA-3851: Automate release notes and include lin...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1670 KAFKA-3851: Automate release notes and include links to upgrade notes for release and most recent docs to forward users of older releases to newest docs. You can merge this pull request into a Git

Re: Kafka 0.10.0.1 plan

Yes, I'll do it. I will certainly take you up on your offer. :) Ismael On Wed, Jul 27, 2016 at 3:58 AM, Gwen Shapira wrote: > Thanks Ismael :) > > I assume you are managing the release (i.e. rolling the RCs and > starting the vote)? Let me know if you need help with the RC

[jira] [Updated] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3996: --- Reviewer: Jun Rao Status: Patch Available (was: In Progress) > ByteBufferMessageSet.writeTo()

[GitHub] kafka pull request #1669: KAFKA-3996: ByteBufferMessageSet.writeTo() should ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1669 KAFKA-3996: ByteBufferMessageSet.writeTo() should be non-blocking Also: * Introduce a blocking variant to be used by `FileMessageSet.append`, * Add tests * Minor clean-ups You can merge

[jira] [Commented] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395055#comment-15395055 ] ASF GitHub Bot commented on KAFKA-3996: --- GitHub user ijuma opened a pull request:

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

See

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

See

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395001#comment-15395001 ] Jiangjie Qin commented on KAFKA-3994: - [~ijuma] ^^ > Deadlock between consumer heartbeat expiration

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395000#comment-15395000 ] Jiangjie Qin commented on KAFKA-3994: - [~hachikuji] This is on the trunk. I will not be able to work

[jira] [Commented] (KAFKA-3852) Clarify how to handle message format upgrade without killing performance

[ https://issues.apache.org/jira/browse/KAFKA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394993#comment-15394993 ] Gwen Shapira commented on KAFKA-3852: - ah, I see you just picked it up. Never mind, then :) > Clarify

[jira] [Commented] (KAFKA-3852) Clarify how to handle message format upgrade without killing performance

[ https://issues.apache.org/jira/browse/KAFKA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394990#comment-15394990 ] Gwen Shapira commented on KAFKA-3852: - Hey [~ewencp], mind if I take a crack at that one? I want to

[jira] [Assigned] (KAFKA-3852) Clarify how to handle message format upgrade without killing performance

[ https://issues.apache.org/jira/browse/KAFKA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-3852: Assignee: Ewen Cheslack-Postava > Clarify how to handle message format

Re: Kafka 0.10.0.1 plan

Thanks Ismael :) I assume you are managing the release (i.e. rolling the RCs and starting the vote)? Let me know if you need help with the RC rollout. I did it fairly recently (41 bugs ago?) Gwen On Tue, Jul 26, 2016 at 7:55 PM, Ismael Juma wrote: > Hi everyone, > > We have

[jira] [Assigned] (KAFKA-3851) Add references to important installation/upgrade notes to release notes

[ https://issues.apache.org/jira/browse/KAFKA-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-3851: Assignee: Ewen Cheslack-Postava > Add references to important

Kafka 0.10.0.1 plan

Hi everyone, We have fixed 41 JIRAs[1] (including a few critical bugs) in the 0.10.0 branch since 0.10.0.0 was released and it would be good to release 0.10.0.1 soon. The current list of issues that have 0.10.0.1 as the target version can be found below:

[jira] [Updated] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

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

[jira] [Commented] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394972#comment-15394972 ] ASF GitHub Bot commented on KAFKA-3500: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #1662: KAFKA-3500: Handle null keys and values in KafkaOf...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1662 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3996: --- Priority: Blocker (was: Major) > ByteBufferMessageSet.writeTo() should be non-blocking >

[jira] [Work started] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3996 started by Ismael Juma. -- > ByteBufferMessageSet.writeTo() should be non-blocking >

[jira] [Updated] (KAFKA-3995) Add a new configuration "enable.comrpession.ratio.estimation" to the producer config

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Description: We recently see a few cases where RecordTooLargeException is thrown because the

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

See

[jira] [Commented] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394923#comment-15394923 ] Ismael Juma commented on KAFKA-3986: Agreed [~sriramsub]. > completedReceives can contain closed

[jira] [Comment Edited] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394923#comment-15394923 ] Ismael Juma edited comment on KAFKA-3986 at 7/27/16 1:50 AM: - Agreed

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394920#comment-15394920 ] Jason Gustafson commented on KAFKA-3994: Good catch [~becket_qin]. Just to clarify, this was not

[jira] [Updated] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3994: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Deadlock between consumer heartbeat

[jira] [Updated] (KAFKA-3689) Exception when attempting to decrease connection count for address with no connections

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3689: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Exception when attempting to

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394919#comment-15394919 ] Ismael Juma commented on KAFKA-3994: Also, did you see this issue with 0.10.0.0 or trunk? > Deadlock

[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > completedReceives can contain closed

[jira] [Updated] (KAFKA-3689) Exception when attempting to decrease connection count for address with no connections

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3689: --- Assignee: (was: Jun Rao) > Exception when attempting to decrease connection count for address with no >

[jira] [Commented] (KAFKA-3986) completedReceives can contain closed channels

[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394900#comment-15394900 ] Sriram Subramanian commented on KAFKA-3986: --- Given that it cannot be consistently reproduced, it

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

See Changes: [ismael] MINOR: Increase default timeout for other `wait` methods in `TestUtils` -- [...truncated 1312 lines...] kafka.server.LogRecoveryTest >

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394836#comment-15394836 ] Ismael Juma commented on KAFKA-3994: [~becket_qin], are you intending to work on this? cc [~hachikuji]

[jira] [Updated] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3733: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Avoid long command lines by setting

[jira] [Updated] (KAFKA-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3585: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Shutdown slow when there is only one

[jira] [Updated] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3437: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > We don't need sitedocs package for

[jira] [Updated] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3500: - Priority: Blocker (was: Critical) > KafkaOffsetBackingStore set method needs to

[jira] [Updated] (KAFKA-3396) Unauthorized topics are returned to the user

[ https://issues.apache.org/jira/browse/KAFKA-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3396: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Unauthorized topics are returned to

[jira] [Updated] (KAFKA-3947) kafka-reassign-partitions.sh should support dumping current assignment

[ https://issues.apache.org/jira/browse/KAFKA-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3947: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > kafka-reassign-partitions.sh should

[jira] [Updated] (KAFKA-3428) Remove metadata sync bottleneck from mirrormaker's producer

[ https://issues.apache.org/jira/browse/KAFKA-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3428: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Remove metadata sync bottleneck from

[jira] [Updated] (KAFKA-3234) Minor documentation edits: clarify minISR; some topic-level configs are missing

[ https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3234: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Minor documentation edits: clarify

[jira] [Updated] (KAFKA-3284) Consider removing beta label in security documentation

[ https://issues.apache.org/jira/browse/KAFKA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3284: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Consider removing beta label in

[jira] [Updated] (KAFKA-3438) Rack Aware Replica Reassignment should warn of overloaded brokers

[ https://issues.apache.org/jira/browse/KAFKA-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3438: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Rack Aware Replica Reassignment

[jira] [Updated] (KAFKA-3493) Replica fetcher load is not balanced over fetcher threads

[ https://issues.apache.org/jira/browse/KAFKA-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3493: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Replica fetcher load is not balanced

[jira] [Updated] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3665: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > Default

[jira] [Updated] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3123: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Follower Broker cannot start if

[jira] [Updated] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3824: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Docs indicate auto.commit breaks at

[jira] [Updated] (KAFKA-3866) KerberosLogin refresh time bug and other improvements

[ https://issues.apache.org/jira/browse/KAFKA-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3866: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > KerberosLogin refresh time bug and

[jira] [Updated] (KAFKA-3374) Failure in security rolling upgrade phase 2 system test

[ https://issues.apache.org/jira/browse/KAFKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3374: --- Fix Version/s: 0.10.0.2 > Failure in security rolling upgrade phase 2 system test >

[jira] [Updated] (KAFKA-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3190: --- Fix Version/s: (was: 0.10.0.1) 0,10.0.2 > KafkaProducer should not invoke

[jira] [Updated] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3135: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > Unexpected delay before fetch

[jira] [Updated] (KAFKA-3374) Failure in security rolling upgrade phase 2 system test

[ https://issues.apache.org/jira/browse/KAFKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3374: --- Fix Version/s: (was: 0.10.0.1) > Failure in security rolling upgrade phase 2 system test >

[GitHub] kafka pull request #1665: MINOR: Increase default timeout for other `wait` m...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1665 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3996: --- Fix Version/s: 0.10.0.1 > ByteBufferMessageSet.writeTo() should be non-blocking >

[jira] [Assigned] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3996: -- Assignee: Ismael Juma > ByteBufferMessageSet.writeTo() should be non-blocking >

[jira] [Updated] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-3973: --- Status: Patch Available (was: In Progress) > Investigate feasibility of caching bytes vs. records >

[GitHub] kafka pull request #1668: Kafka 3973 feasibility caching bytes vs records

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/1668 Kafka 3973 feasibility caching bytes vs records @enothereska Added the benchmark test per comments. Thanks You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-3973) Investigate feasibility of caching bytes vs. records

[ https://issues.apache.org/jira/browse/KAFKA-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394761#comment-15394761 ] Bill Bejeck commented on KAFKA-3973: [~ijuma] I re-ran the tests with no instrumentation using the

[jira] [Commented] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

[ https://issues.apache.org/jira/browse/KAFKA-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394755#comment-15394755 ] Jun Rao commented on KAFKA-3996: To address this issue, we will need to get rid of the while loop and

[jira] [Created] (KAFKA-3996) ByteBufferMessageSet.writeTo() should be non-blocking

Jun Rao created KAFKA-3996: -- Summary: ByteBufferMessageSet.writeTo() should be non-blocking Key: KAFKA-3996 URL: https://issues.apache.org/jira/browse/KAFKA-3996 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-3995) Add a new configuration "enable.comrpession.ratio.estimation" to the producer config

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-3995: -- Assignee: Mayuresh Gharat > Add a new configuration

[jira] [Created] (KAFKA-3995) Add a new configuration "enable.comrpession.ratio.estimation" to the producer config

Jiangjie Qin created KAFKA-3995: --- Summary: Add a new configuration "enable.comrpession.ratio.estimation" to the producer config Key: KAFKA-3995 URL: https://issues.apache.org/jira/browse/KAFKA-3995

[jira] [Created] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

Jiangjie Qin created KAFKA-3994: --- Summary: Deadlock between consumer heartbeat expiration and offset commit. Key: KAFKA-3994 URL: https://issues.apache.org/jira/browse/KAFKA-3994 Project: Kafka

[jira] [Assigned] (KAFKA-2806) Allow Kafka System Tests under different JDK versions

[ https://issues.apache.org/jira/browse/KAFKA-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-2806: Assignee: Ewen Cheslack-Postava > Allow Kafka System Tests under different

[jira] [Commented] (KAFKA-3993) Console producer drops data

[ https://issues.apache.org/jira/browse/KAFKA-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394244#comment-15394244 ] ASF GitHub Bot commented on KAFKA-3993: --- GitHub user theduderog opened a pull request:

[GitHub] kafka pull request #1667: KAFKA-3993 Console Producer Drops Data

GitHub user theduderog opened a pull request: https://github.com/apache/kafka/pull/1667 KAFKA-3993 Console Producer Drops Data @ijuma Would you mind taking a look? This fixes the problem for me using this test script. ``` export

[jira] [Created] (KAFKA-3993) Console producer drops data

Roger Hoover created KAFKA-3993: --- Summary: Console producer drops data Key: KAFKA-3993 URL: https://issues.apache.org/jira/browse/KAFKA-3993 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3991) MirrorMaker: allow custom publisher

[ https://issues.apache.org/jira/browse/KAFKA-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394075#comment-15394075 ] ASF GitHub Bot commented on KAFKA-3991: --- GitHub user hsun-cnnxty opened a pull request:

[GitHub] kafka pull request #1666: [KAFKA-3991]: allow MirrorMaker to have custom pro...

GitHub user hsun-cnnxty opened a pull request: https://github.com/apache/kafka/pull/1666 [KAFKA-3991]: allow MirrorMaker to have custom producer Please see jira: https://issues.apache.org/jira/browse/KAFKA-3991 You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393962#comment-15393962 ] Manikumar Reddy commented on KAFKA-3992: looks like you are giving same client-Id (consumerId) to

[jira] [Updated] (KAFKA-3374) Failure in security rolling upgrade phase 2 system test

[ https://issues.apache.org/jira/browse/KAFKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3374: - Fix Version/s: 0.10.0.1 > Failure in security rolling upgrade phase 2 system test

[jira] [Commented] (KAFKA-3374) Failure in security rolling upgrade phase 2 system test

[ https://issues.apache.org/jira/browse/KAFKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393912#comment-15393912 ] Ewen Cheslack-Postava commented on KAFKA-3374: -- There's also a few cases of this on the

[jira] [Commented] (KAFKA-3980) JmxReporter uses excessive memory causing OutOfMemoryException

[ https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393877#comment-15393877 ] Andrew Jorgensen commented on KAFKA-3980: - [~omkreddy] do you mean enable debug log on the

[jira] [Created] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

Alexander Cook created KAFKA-3992: - Summary: InstanceAlreadyExistsException Error for Consumers Starting in Parallel Key: KAFKA-3992 URL: https://issues.apache.org/jira/browse/KAFKA-3992 Project:

[jira] [Created] (KAFKA-3991) MirrorMaker: allow custom publisher

Hang Sun created KAFKA-3991: --- Summary: MirrorMaker: allow custom publisher Key: KAFKA-3991 URL: https://issues.apache.org/jira/browse/KAFKA-3991 Project: Kafka Issue Type: Improvement

Re: [GitHub] kafka pull request #1661: KAFKA-3987: Allow config of the hash algorithm use...

Hi Could somebody with commit permission review (and eventually merge) this pull request? Regards Luciano On Mon, Jul 25, 2016 at 11:49 AM, luafran wrote: > GitHub user luafran opened a pull request: > > https://github.com/apache/kafka/pull/1661 > > KAFKA-3987:

[jira] [Commented] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393625#comment-15393625 ] Ismael Juma commented on KAFKA-3990: The buffer is allocated based on the size returned by the broker.

[jira] [Updated] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brice Dutheil updated KAFKA-3990: - Description: We are regularly seeing OOME errors on a kafka producer, we first saw : {code}

[jira] [Created] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

Brice Dutheil created KAFKA-3990: Summary: Kafka New Producer may raise an OutOfMemoryError Key: KAFKA-3990 URL: https://issues.apache.org/jira/browse/KAFKA-3990 Project: Kafka Issue Type:

Re: [VOTE] KIP-55: Secure quotas for authenticated users

Hi all, This vote has passed with 3 binding and one non-binding +1. Many thanks to those who voted. If you have any comments or suggestions, please continue to add them to the discussion thread. On Fri, Jul 15, 2016 at 6:47 AM, Gwen Shapira wrote: > +1 > > Thanks for

[GitHub] kafka pull request #1665: MINOR: Increase default timeout for other `wait` m...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1665 MINOR: Increase default timeout for other `wait` methods in `TestUtils` They are now consistent with `waitUntilTrue`. You can merge this pull request into a Git repository by running: $ git pull