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

2017-11-20 Thread kaushik srinivas (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260268#comment-16260268 ] kaushik srinivas commented on KAFKA-6165: - yes. Can the OutOfMemoryError stack trace thrown be

[jira] [Updated] (KAFKA-5943) Reduce dependency on mock in connector tests

2017-11-20 Thread Ted Yu (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-5943: -- Description: Currently connector tests make heavy use of mock (easymock, power mock). This may hide the real

[jira] [Commented] (KAFKA-4857) Replace StreamsKafkaClient with AdminClient in Kafka Streams

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

[jira] [Commented] (KAFKA-4893) async topic deletion conflicts with max topic length

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

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

2017-11-20 Thread Daniel Lee (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260050#comment-16260050 ] Daniel Lee commented on KAFKA-5153: --- [~ijuma] Just wanted to confirm that upgrading to 0.11.0.1 resolved

[jira] [Commented] (KAFKA-6170) Add the AdminClient in Streams' KafkaClientSupplier

2017-11-20 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259720#comment-16259720 ] ASF GitHub Bot commented on KAFKA-6170: --- Github user asfgit closed the pull request at:

[jira] [Commented] (KAFKA-6247) Fix system test dependency issues

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

[jira] [Created] (KAFKA-6247) Fix system test dependency issues

2017-11-20 Thread Colin P. McCabe (JIRA)
Colin P. McCabe created KAFKA-6247: -- Summary: Fix system test dependency issues Key: KAFKA-6247 URL: https://issues.apache.org/jira/browse/KAFKA-6247 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6195) DNS alias support for secured connections

2017-11-20 Thread Rajini Sivaram (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259656#comment-16259656 ] Rajini Sivaram commented on KAFKA-6195: --- [~jonathanskrzypek] It may be possible to create keytabs

[jira] [Commented] (KAFKA-6239) Consume group hung into rebalancing state, now stream not able to poll data

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259631#comment-16259631 ] Matthias J. Sax commented on KAFKA-6239: How is this different to KAFKA-6236 ? > Consume group

[jira] [Updated] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6237: --- Labels: exactly-once (was: ) > stream stopped working after exception: Cannot execute

[jira] [Updated] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6237: --- Component/s: core > stream stopped working after exception: Cannot execute transactional

[jira] [Comment Edited] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259618#comment-16259618 ] Matthias J. Sax edited comment on KAFKA-6237 at 11/20/17 6:38 PM: -- Thanks

[jira] [Reopened] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-6237: > stream stopped working after exception: Cannot execute transactional method > because we are

[jira] [Resolved] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6237. Resolution: Duplicate Thanks for reporting this. It is a duplicate and the issue is fixed

[jira] [Updated] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6237: --- Component/s: streams > stream stopped working after exception: Cannot execute transactional

[jira] [Commented] (KAFKA-6236) stream not picking data from topic - after rebalancing

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259612#comment-16259612 ] Matthias J. Sax commented on KAFKA-6236: Thanks for reporting this. What is the reason for your

[jira] [Updated] (KAFKA-6236) stream not picking data from topic - after rebalancing

2017-11-20 Thread Matthias J. Sax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6236: --- Component/s: streams > stream not picking data from topic - after rebalancing >

[jira] [Assigned] (KAFKA-6234) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpoint

2017-11-20 Thread Guozhang Wang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-6234: Assignee: Sönke Liebau > Transient failure in >

[jira] [Created] (KAFKA-6246) Enable reconfiguration of listeners and security configs

2017-11-20 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-6246: - Summary: Enable reconfiguration of listeners and security configs Key: KAFKA-6246 URL: https://issues.apache.org/jira/browse/KAFKA-6246 Project: Kafka

[jira] [Created] (KAFKA-6245) Enable reconfiguration of default topic configs used by brokers

2017-11-20 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-6245: - Summary: Enable reconfiguration of default topic configs used by brokers Key: KAFKA-6245 URL: https://issues.apache.org/jira/browse/KAFKA-6245 Project: Kafka

[jira] [Created] (KAFKA-6243) Enable reconfiguration of metrics reporters and their custom configs

2017-11-20 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-6243: - Summary: Enable reconfiguration of metrics reporters and their custom configs Key: KAFKA-6243 URL: https://issues.apache.org/jira/browse/KAFKA-6243 Project: Kafka

[jira] [Updated] (KAFKA-6241) Enable dynamic reconfiguration of SSL keystores

2017-11-20 Thread Rajini Sivaram (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-6241: -- Description: See

[jira] [Created] (KAFKA-6242) Enable resizing various broker thread pools

2017-11-20 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-6242: - Summary: Enable resizing various broker thread pools Key: KAFKA-6242 URL: https://issues.apache.org/jira/browse/KAFKA-6242 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6241) Enable dynamic reconfiguration of SSL keystores

2017-11-20 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-6241: - Summary: Enable dynamic reconfiguration of SSL keystores Key: KAFKA-6241 URL: https://issues.apache.org/jira/browse/KAFKA-6241 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6240) Support dynamic updates of frequently updated broker configs

2017-11-20 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-6240: - Summary: Support dynamic updates of frequently updated broker configs Key: KAFKA-6240 URL: https://issues.apache.org/jira/browse/KAFKA-6240 Project: Kafka

[jira] [Commented] (KAFKA-6199) Single broker with fast growing heap usage

2017-11-20 Thread Robin Tweedie (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259208#comment-16259208 ] Robin Tweedie commented on KAFKA-6199: -- I think I found the corresponding "old client" causing this

[jira] [Created] (KAFKA-6239) Consume group hung into rebalancing state, now stream not able to poll data

2017-11-20 Thread DHRUV BANSAL (JIRA)
DHRUV BANSAL created KAFKA-6239: --- Summary: Consume group hung into rebalancing state, now stream not able to poll data Key: KAFKA-6239 URL: https://issues.apache.org/jira/browse/KAFKA-6239 Project:

[jira] [Updated] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DHRUV BANSAL updated KAFKA-6237: Description: 017-11-19 07:52:44,673

[jira] [Commented] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259176#comment-16259176 ] DHRUV BANSAL commented on KAFKA-6237: - Also when I see the state of the corresponding consumer group

[jira] [Updated] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DHRUV BANSAL updated KAFKA-6237: Description: 017-11-19 07:52:44,673

[jira] [Commented] (KAFKA-6223) Please delete old releases from mirroring system

2017-11-20 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259127#comment-16259127 ] Ismael Juma commented on KAFKA-6223: We still host all the release versions and the links work from

[jira] [Commented] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259123#comment-16259123 ] DHRUV BANSAL commented on KAFKA-6237: - I have attached nohup.logs for now from 1 of my broker (in

[jira] [Updated] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DHRUV BANSAL updated KAFKA-6237: Attachment: nohup.out > stream stopped working after exception: Cannot execute transactional method

[jira] [Commented] (KAFKA-6238) Issues with protocol version when applying a rolling upgrade to 1.0.0

2017-11-20 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259120#comment-16259120 ] Ismael Juma commented on KAFKA-6238: [~hachikuji], can you please submit a fix? > Issues with

[jira] [Assigned] (KAFKA-6238) Issues with protocol version when applying a rolling upgrade to 1.0.0

2017-11-20 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-6238: -- Assignee: Jason Gustafson > Issues with protocol version when applying a rolling upgrade to

[jira] [Commented] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259116#comment-16259116 ] DHRUV BANSAL commented on KAFKA-6237: - which logs you are refering to exactly? server.log or

[jira] [Created] (KAFKA-6238) Issues with protocol version when applying a rolling upgrade to 1.0.0

2017-11-20 Thread JIRA
Diego Louzán created KAFKA-6238: --- Summary: Issues with protocol version when applying a rolling upgrade to 1.0.0 Key: KAFKA-6238 URL: https://issues.apache.org/jira/browse/KAFKA-6238 Project: Kafka

[jira] [Commented] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread Damian Guy (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259072#comment-16259072 ] Damian Guy commented on KAFKA-6237: --- Hi, can you please include the broker logs? This doesn't look like

[jira] [Created] (KAFKA-6237) stream stopped working after exception: Cannot execute transactional method because we are in an error state

2017-11-20 Thread DHRUV BANSAL (JIRA)
DHRUV BANSAL created KAFKA-6237: --- Summary: stream stopped working after exception: Cannot execute transactional method because we are in an error state Key: KAFKA-6237 URL:

[jira] [Resolved] (KAFKA-1130) "log.dirs" is a confusing property name

2017-11-20 Thread JIRA
[ https://issues.apache.org/jira/browse/KAFKA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-1130. - Resolution: Won't Fix Due to the age of the last comment on this issue and the fact that there