[jira] [Created] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

2017-11-07 Thread Brett Rann (JIRA)
Brett Rann created KAFKA-6185: - Summary: java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients Key: KAFKA-6185 URL: https://issues.apache.org/jira/browse/KAFKA-6185

[jira] [Updated] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

2017-11-07 Thread Brett Rann (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Rann updated KAFKA-6185: -- Description: We are testing 1.0.0 in a couple of environments. Both have about 5 brokers, with two

[jira] [Updated] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

2017-11-07 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-6146: Summary: minimize the number of triggers enqueuing PreferredReplicaLeaderElection events (was:

[jira] [Commented] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

2017-11-07 Thread Manikumar (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243434#comment-16243434 ] Manikumar commented on KAFKA-6185: -- Can we take periodic output of the below given jmap command?. This

[jira] [Updated] (KAFKA-6185) java.lang.OutOfMemoryError memory leak on 1.0.0 with 0.11.0.1 on disk and converting to 0.9 clients

2017-11-07 Thread Brett Rann (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Rann updated KAFKA-6185: -- Description: We are testing 1.0.0 in a couple of environments. Both have about 5 brokers, with two

[jira] [Assigned] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

2017-11-07 Thread Vahid Hashemian (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-6184: -- Assignee: Vahid Hashemian > report a metric of the lag between the consumer offset and

[jira] [Comment Edited] (KAFKA-6024) Consider moving validation in KafkaConsumer ahead of call to acquireAndEnsureOpen()

2017-11-07 Thread Ted Yu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222620#comment-16222620 ] Ted Yu edited comment on KAFKA-6024 at 11/8/17 1:40 AM: +1 was (Author:

[jira] [Commented] (KAFKA-6042) Kafka Request Handler deadlocks and brings down the cluster.

2017-11-07 Thread Brett Rann (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243339#comment-16243339 ] Brett Rann commented on KAFKA-6042: --- I have the same memory issue [~corlettb] has described. I've

[jira] [Updated] (KAFKA-6146) re-register the exist watch on PreferredReplicaElectionZNode only after the preferred leader election completes

2017-11-07 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-6146: Summary: re-register the exist watch on PreferredReplicaElectionZNode only after the preferred

[jira] [Commented] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

2017-11-07 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242959#comment-16242959 ] ASF GitHub Bot commented on KAFKA-6146: --- GitHub user onurkaraman opened a pull request:

[jira] [Created] (KAFKA-6184) report a metric of the lag between the consumer offset and the start offset of the log

2017-11-07 Thread Jun Rao (JIRA)
Jun Rao created KAFKA-6184: -- Summary: report a metric of the lag between the consumer offset and the start offset of the log Key: KAFKA-6184 URL: https://issues.apache.org/jira/browse/KAFKA-6184 Project:

[jira] [Updated] (KAFKA-6182) Automatic co-partitioning of topics via automatic intermediate topic with matching partitions

2017-11-07 Thread Antony Stubbs (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6182: - Affects Version/s: 1.0.0 > Automatic co-partitioning of topics via automatic intermediate topic

[jira] [Comment Edited] (KAFKA-6158) CONSUMER-ID and HOST values are concatenated if the CONSUMER-ID is > 50 chars

2017-11-07 Thread Vahid Hashemian (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235878#comment-16235878 ] Vahid Hashemian edited comment on KAFKA-6158 at 11/7/17 11:03 PM: -- Those

[jira] [Assigned] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

2017-11-07 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman reassigned KAFKA-6146: --- Assignee: Onur Karaman > minimize the number of triggers enqueuing

[jira] [Updated] (KAFKA-6110) Warning when running the broker on Windows

2017-11-07 Thread Vahid Hashemian (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-6110: --- Fix Version/s: (was: 1.1.0) > Warning when running the broker on Windows >

[jira] [Updated] (KAFKA-6146) minimize the number of triggers enqueuing PreferredReplicaLeaderElection events

2017-11-07 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-6146: Description: We currently enqueue a PreferredReplicaLeaderElection controller event in

[jira] [Updated] (KAFKA-6146) re-register the exist watch on PreferredReplicaElectionZNode after the preferred leader election completes

2017-11-07 Thread Onur Karaman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-6146: Description: We currently enqueue a PreferredReplicaLeaderElection controller event in

[jira] [Resolved] (KAFKA-6110) Warning when running the broker on Windows

2017-11-07 Thread Vahid Hashemian (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian resolved KAFKA-6110. Resolution: Duplicate Fix Version/s: 1.1.0 > Warning when running the broker on

[jira] [Commented] (KAFKA-6110) Warning when running the broker on Windows

2017-11-07 Thread Vahid Hashemian (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242814#comment-16242814 ] Vahid Hashemian commented on KAFKA-6110: That's right. Thanks. I'll mark this as duplicate. >

[jira] [Created] (KAFKA-6183) Broker should send OffsetCommitResponse only after it has written offset to cache

2017-11-07 Thread Dong Lin (JIRA)
Dong Lin created KAFKA-6183: --- Summary: Broker should send OffsetCommitResponse only after it has written offset to cache Key: KAFKA-6183 URL: https://issues.apache.org/jira/browse/KAFKA-6183 Project: Kafka

[jira] [Assigned] (KAFKA-4950) ConcurrentModificationException when iterating over Kafka Metrics

2017-11-07 Thread Vahid Hashemian (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4950: -- Assignee: Sébastien Launay (was: Vahid Hashemian) > ConcurrentModificationException

[jira] [Commented] (KAFKA-6180) AbstractConfig.getList() should never return null

2017-11-07 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242570#comment-16242570 ] ASF GitHub Bot commented on KAFKA-6180: --- GitHub user lahabana opened a pull request:

[jira] [Updated] (KAFKA-6182) Automatic co-partitioning of topics via automatic intermediate topic with matching partitions

2017-11-07 Thread Antony Stubbs (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antony Stubbs updated KAFKA-6182: - Description: Currently it is up to the user to ensure that two input topics for a join have the

[jira] [Created] (KAFKA-6181) Examining log messages with {{--deep-iteration}} should show superset of fields

2017-11-07 Thread Yeva Byzek (JIRA)
Yeva Byzek created KAFKA-6181: - Summary: Examining log messages with {{--deep-iteration}} should show superset of fields Key: KAFKA-6181 URL: https://issues.apache.org/jira/browse/KAFKA-6181 Project:

[jira] [Created] (KAFKA-6180) AbstractConfig.getList() should never return null

2017-11-07 Thread Charly Molter (JIRA)
Charly Molter created KAFKA-6180: Summary: AbstractConfig.getList() should never return null Key: KAFKA-6180 URL: https://issues.apache.org/jira/browse/KAFKA-6180 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

2017-11-07 Thread Michal Klempa (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241823#comment-16241823 ] Michal Klempa commented on KAFKA-3355: -- Hi, anything new on this? I am running into same issue with

[jira] [Commented] (KAFKA-6174) Add methods in Options classes to keep binary compatibility between 0.11 and 1.0

2017-11-07 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241779#comment-16241779 ] Ismael Juma commented on KAFKA-6174: [~tombentley], yes, there is a JIRA and proof of concept PR for

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

2017-11-07 Thread kaushik srinivas (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241745#comment-16241745 ] kaushik srinivas commented on KAFKA-6165: - Hi huxihx, Thanks for the feedback. Initially when

[jira] [Updated] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

2017-11-07 Thread kaushik srinivas (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kaushik srinivas updated KAFKA-6165: Attachment: kafkaServer-gc.log kafkaServer-gc_agent03.log